pry-nav
pry-nav copied to clipboard
nixme
Binding navigation commands for Pry to make a simple debugger
Why is pry-nav discouraged for MRI? Per the README: > Using MRI? We recommend break or pry-byebug instead! pry-byebug has some issue with zeitwerk
"next" performs a "step" in jruby. Anyone have any pointers on how I might begin to tackle this?
I was `next`ing a line of code which threw me into mon_synchronize line 213 "mon_exit" ``` 208: def mon_synchronize 209: mon_enter 210: begin 211: yield 212: ensure => 213: mon_exit...
Pry's step function has a namespace collision with cucumber's step function. Calling step when inside a binding pry from within cucumber causes an infinite loop. Setting an alias doesn't help....
Hi, as of tonight (25 jan) pry 0.9.8 has been released. I haven't tested thoroughly but it appears `pry-nav` still seems to work ok. I have also officially released [pry-stack_explorer](https://github.com/banister/pry-stack_explorer)...
### Description This PR removes the dependency on pry < 0.15. ### Reason for PR: I get this warning after upgrading to Ruby 3.4.1: ``` versions/3.4.1/lib/ruby/gems/3.4.0/gems/pry-0.14.2/lib/pry/command_state.rb:3: warning: .rbenv/versions/3.4.1/lib/ruby/3.4.0/ostruct.rb was loaded...
this gem is one of my gem dependencies. It blocked my gem upgrade to support pry 1.15. Thanks.
