What does `next' means? Thanks. about pry-byebug HOT 10 CLOSED

i found that removing pry-nav from my gemfile returned functionality to next. see also: #9

from pry-byebug.

Hi @zw963, sorry for taking such a long time to get back to you.

Regarding the first issue you describe, pry-byebug behaves just like byebug: step steps into the for loop while next jumps over it. I think the behaviour is fine.

Regarding the second issue, the same thing can be observed in byebug. It looks when doing (1..10), the TracePoint API generates a duplicated line event, for some reason. I will further investigate this and report it to ruby-head if necessary. If you use only byebug, you can workaround this using set forcestep that will always move to a new line when stepping/nexting. Unfortunately, this is not available in pry-byebug.

Cheers!

from pry-byebug.

@zw963 I've reported the bug about the duplicate events to ruby-core: https://bugs.ruby-lang.org/issues/10449

from pry-byebug.

Thank you for you reply !

from pry-byebug.

@zw963 The bug has already been fixed, but I'm going to wait for 2.2 to be released to confirm we can close this.

from pry-byebug.

@davidrunger Could you confirm this issue is solved in Ruby 2.2.0?

from pry-byebug.

Yes, I can confirm that, with Ruby 2.2.0, I no longer have the issue that I was having before of getting "stuck" at a line with parentheses and having to type next/step an extra time to advance forward in the code. Thanks for following up!

I tested using:
Ruby 2.2.0 (the official release, obtained via rbenv)
byebug 3.5.1
pry-byebug 2.0.0
pry 0.10.1

from pry-byebug.

Thanks for testing! I'll go ahead and close this, then.

from pry-byebug.

Thanks a lot for all.

from pry-byebug.

@zw963 No problem! 😄

from pry-byebug.