Compatibility with pry-nav

[marcferna]

trafficstars

Is it compatible with pry-nav? I can't make it to work, when I "next" or "step" it goes into PryRemote code

From: @ line 128 PryRemote::Server#run:

      124: def run
      125:   setup
      126:   Pry.start(@object, :input => client.input_proxy, :output => client.output)
      127: ensure
   => 128:   teardown
      129: end

[yock]

I've been seeing this same behavior recently. Using:

• Ruby 2.0.0
• Rails 3.2.13
• Pry 0.9.10
• Pry-Nav 0.2.3
• Pry-Remote 0.1.7.

[drn]

+1. Been getting the same issue with

• Ruby 2.0.0p0
• rails (3.2.13)
• pry (0.9.12)
• pry-nav (0.2.3)
• pry-rails (0.2.2)
• pry-remote (0.1.6)

Thanks! Let me know if there's anything we can help with

[RobinDaugherty]

Also experiencing this issue with

• Ruby 2.0.0-p195 and 2.0.0-p0
• rails (3.2.13)
• pry (0.9.12.2)
• pry-rails (0.3.1)
• pry-remote (0.1.7)
• pry-stack_explorer (0.4.9)
• debugger (1.6.0)
• pry-debugger (0.2.2)

And with:

• byebug (1.4.0)
• pry-byebug (1.1.0)

[Mon-Ouie]

Hey,

I'm not certain where the issue is located. pry-nav seems to have code in it to handle pry-remote (https://github.com/nixme/pry-nav/blob/master/lib/pry-nav/pry_remote_ext.rb). Maybe that has been broken since then?

[deivid-rodriguez]

• pry-nav has been deprecated in favor of pry-debugger for ruby >= 1.9.2 as you can read in its README. So you should not expect that to work.
• pry-debugger is currently broken for ruby-2.0.0. The most common issue is next and step stopping in random places, like in this case.
• pry-byebug removed support for pry-remote when it was first released because I was having some trouble to make that work and I had never used that feature. I will try to bring this functionality back when I find time.

So I might be wrong but I don't think this is an issue with pry-remote.

Salute.