-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pry-rescue doesn't work correctly if pry-byebug is loaded #71
pry-rescue doesn't work correctly if pry-byebug is loaded #71
Comments
I just ran into the same issue, is there a fix for this? |
Anyone fixed this? |
Same problem here. Any workarounds? |
I downgraded especially to 3.1 |
Thanks for the tip. Just realised I don't have byebug in the mix at the moment :) will log as a new issue. |
There are many issues like this caused by the fact that pry-byebug changes pry so that it advances to the next line after a breakpoint is hit. See the discussion here: deivid-rodriguez/pry-byebug#45 |
@hakunin @magicalbanana Other than downgrading (3.1 is the latest version of pry-byebug, I figure @magicalbanana meant 3.0.1 or from 3.1, I am not sure), I found an alternative workaround: disabling this annoying auto-loading of plugins and then loading it manually (now I can use the executable). I'd like to register it here for people that like me arrive here unaware of this "convenience". |
Here's a patched pry 0.10.2pre to add more config tweaks (i.e., blacklisting plugins) via env vars and how to get it. |
Works for me with pry-byebug 3.4.0 and pry-rescue 1.4.4. |
I have pry-byebug 3.4.0 and pry-rescue 1.4.4 - and I have the same problem with ruby 2.3.1 |
In combination with https://github.com/russelldavis/pry-byebug/pull/1/files, makes pry-rescue work when using pry-byebug. Fixes ConradIrwin#71
Still getting this as of 26/01/2017, any news? |
Adapted from JoshCheek code at deivid-rodriguez#45 This fixes ConradIrwin/pry-rescue#71
pry-byebug overwrites Pry.start and pry-rescue doesn't work correctly if pry-byebug is loaded, as you can see below:
My Gemfile.lock is here:
The text was updated successfully, but these errors were encountered: