Gopal Patel

I believe using instance variables to share data to the view is another "wart" / design decision that this project doesn't agree with and adds another boundary. Use `expose` as...

What about using `throw`/`catch` instead?

Hrm... with all the incompatibility with 2.0 and others asking for byebug, I think I'll create a branch without pry-debugger and folks can drop in whichever debug mechanism they want....

Okay. A branch based off 0.5.2 is available at https://github.com/nixme/jazz_hands/tree/bring-your-own-debugger You can use it in bundler via: ``` ruby gem 'jazz_hands', github: 'nixme/jazz_hands', branch: 'bring-your-own-debugger' ``` I might release that...

Sorry, taking a look now. I do want this functionality in master

Probably although I can use this as a blueprint. Sorry been behind on my projects. I have time this Thanksgiving holiday to look at everything and merge.

Yes, we have to use `SIDEKIQ_PRELOAD=` as well or it won't boot. `SIDEKIQ_PRELOAD= SIDEKIQ_PRELOAD_APP=1` works fine. We're on rails 5.2.4.4. So I did some digging. It comes down to some...

Hrm maybe something changed with Slop, which is what Pry uses to parse commands. For now, you should be able to do `break foo.rb:3 if x == 2`

Awesome. I'll test it out and see if I can come up with a workaround for the segfault.

@banister, are there any open issues on `binding_of_caller` that might be causing the segfaults? `set_trace_func` is pretty finicky in the ruby interpreter though, but I just don't want to rule...