search

nixme / pry-nav

Binding navigation commands for Pry to make a simple debugger
MIT License
390 stars 35 forks source link

pry-nav does not work with the latest version of pry #35

Closed cdhagmann closed 2 years ago

cdhagmann commented 4 years ago

Bundler could not find compatible versions for gem "pry": In Gemfile: pry (~> 0.13.1)

pry-nav was resolved to 0.3.0, which depends on
  pry (>= 0.9.10, < 0.13.0)
iloveitaly commented 3 years ago

@cdhagmann this is fixed on master, give it a try and let me know what you think! We'll release a new version via rubygems soon.

makikata commented 3 years ago

@iloveitaly thank you I use it daily and it works like a charm!!! With a but ;)

I do not know which one of the repository below should I create an issue, thus commenting here as it is related. Otherwise please advise.

Based on this comment, it seems that the pry-byebug fork works with pry-remote. However it looks like combining below, breaks pry-nav.

Basically using next, or step it just skips the whole stack and goes at.

From: /home/user/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/pry-remote-0.1.8/lib/pry-remote.rb:211 PryRemote::Server#run:

    206: def run
    207:   setup
    208: 
    209:   Pry.start(@object, @options.merge(:input => client.input_proxy, :output => client.output))
    210: ensure
 => 211:   teardown
    212: end

This ONLY happens if I am using pry-remote

PS: I was commenting here because I felt it has something to do with the commands sent by pry-nav

iloveitaly commented 3 years ago

@makikata are you on MRI ruby or another ruby runtime?

makikata commented 3 years ago

@iloveitaly I am on MRI 3.0.1

EDIT: I did further testing today and it has nothing to do with pry-nav itself. Removing pry-nav from my Gemfile has the same result.

So please ignore

iloveitaly commented 2 years ago

Closing this out