Open abicky opened 10 years ago
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: https://github.com/deivid-rodriguez/pry-byebug/issues/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
Still getting this as of 26/01/2017, any news?
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: