nixme/pry-nav

Issues

• Can't escape from eval with next

  #20 opened 2 years ago by sam452
  20

• So I removed pry-nav and I got these issues

  #40 opened 2 years ago by gpares
  0

• Why is pry-nav discouraged for MRI?

  #41 opened 3 years ago by justin808
  3

• Debug a each with next

  #25 opened 3 years ago by thiagogsr
  1

• pry-nav does not work with the latest version of pry

  #35 opened 3 years ago by cdhagmann
  5

• stuck on old version of pry

  #38 opened 3 years ago by sshock
  7

• Installing pry-nav makes pry croak with "SystemStackError"

  #17 opened 3 years ago by rcs
  6

• check_file_context broken when path has parenthesis

  #23 opened 3 years ago by eboswort
  1

• Release 0.2.5 with pry <12 support?

  #30 opened 6 years ago by flyinbutrs
  4

• BUG: 404 error on Landing page

  #28 opened 8 years ago by Cwrayzee
  0

• 'next' steps into Pry code after done with app code

  #11 opened 9 years ago by sent-hil
  2

• "next" performs a "step" in jruby

  #19 opened 12 years ago by gregors
  12

• Step "one level back"?

  #15 opened 12 years ago by jmuheim
  4

• Unable to activate pry-nav-0.2.3, because pry-1.0.0.pre1 conflicts with pry (~> 0.9.10) (Gem::LoadError)

  #21 opened 10 years ago by alladi
  2

• Segmentation fault

  #8 opened 13 years ago by ylluminate
  19

• Release a new gem for 0.9.10 Pry release

  #16 opened 12 years ago by banister
  2

• Thread safety

  #2 opened 13 years ago by nixme
  13

• Pry step function namespace collision with cucumber

  #14 opened 13 years ago by daveroberts
  5

• Sadness

  #9 opened 13 years ago by trans
  5

• Assignment to 'c' is confused with abbreviated 'continue' command

  #3 opened 13 years ago by rparker
  10

• pry-nav is having problems with pry-remote

  #10 opened 13 years ago by mrinterweb
  7

• pry-stack_explorer compatibility

  #4 opened 13 years ago by banister
  9

• **next** on last line in a script never cleans up DRb with pry-remote

  #1 opened 13 years ago by nixme
  0