nixme/pry-nav issues and pull requests

#43 - Fix broken link in README.md

Pull Request - State: closed - Opened by justin808 almost 3 years ago

#42 - Update README.md to adjust MRI recommendation

Pull Request - State: closed - Opened by justin808 almost 3 years ago

#41 - Why is pry-nav discouraged for MRI?

Issue - State: open - Opened by justin808 almost 3 years ago - 3 comments

#40 - So I removed pry-nav and I got these issues

Issue - State: closed - Opened by gpares almost 3 years ago

#39 - Remove duplicate required_ruby_version from gemspec

Pull Request - State: closed - Opened by ivoanjo about 3 years ago

#38 - stuck on old version of pry

Issue - State: closed - Opened by sshock over 3 years ago - 7 comments

#37 - Remove the upper bound of pry version

Pull Request - State: closed - Opened by rrosenblum over 3 years ago

#36 - Eliminate eval(FILE) warning for Ruby 2.6+

Pull Request - State: closed - Opened by zxiest almost 4 years ago

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

Issue - State: closed - Opened by cdhagmann about 4 years ago - 5 comments

#34 - bump pry

Pull Request - State: closed - Opened by ericlarosa about 4 years ago

#33 - Update pry dependency to `< 0.14.0`

Pull Request - State: closed - Opened by aliismayilov over 4 years ago - 4 comments

#32 - Fix ruby 2.7 warning

Pull Request - State: closed - Opened by aliismayilov over 4 years ago - 1 comment

#31 - Allow newer versions of pry to be used

Pull Request - State: closed - Opened by rrosenblum over 5 years ago - 2 comments

#30 - Release 0.2.5 with pry <12 support?

Issue - State: closed - Opened by flyinbutrs over 6 years ago - 4 comments

#29 - Allow newer versions of pry to be used

Pull Request - State: closed - Opened by rrosenblum over 6 years ago - 6 comments

#28 - BUG: 404 error on Landing page

Issue - State: closed - Opened by Cwrayzee almost 8 years ago

#27 - Drop support for old ruby versions (< 2.1)

Pull Request - State: closed - Opened by ivoanjo about 8 years ago - 3 comments

#26 - Update README to mention JRuby and fix circular require warning

Pull Request - State: closed - Opened by ivoanjo about 8 years ago - 4 comments

#25 - Debug a each with next

Issue - State: closed - Opened by thiagogsr almost 9 years ago - 1 comment

#24 - Add instructions for JRuby in README

Pull Request - State: closed - Opened by camertron over 9 years ago - 2 comments

#23 - check_file_context broken when path has parenthesis

Issue - State: closed - Opened by eboswort almost 10 years ago - 1 comment

#22 - Allowing pry 0.10.x

Pull Request - State: closed - Opened by jasonrclark about 10 years ago - 4 comments

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

Issue - State: closed - Opened by alladi over 10 years ago - 2 comments

#20 - Can't escape from eval with next

Issue - State: closed - Opened by sam452 over 11 years ago - 20 comments

#19 - "next" performs a "step" in jruby

Issue - State: open - Opened by gregors over 11 years ago - 12 comments

#18 - Safer monkey-patching of Pry.start/.teardown

Pull Request - State: closed - Opened by benizi almost 12 years ago - 1 comment

#17 - Installing pry-nav makes pry croak with "SystemStackError"

Issue - State: closed - Opened by rcs about 12 years ago - 6 comments

#16 - Release a new gem for 0.9.10 Pry release

Issue - State: closed - Opened by banister about 12 years ago - 2 comments

#15 - Step "one level back"?

Issue - State: closed - Opened by jmuheim about 12 years ago - 4 comments

#14 - Pry step function namespace collision with cucumber

Issue - State: open - Opened by daveroberts over 12 years ago - 5 comments

#13 - update dependency for most recent pry release

Pull Request - State: closed - Opened by banister over 12 years ago - 8 comments

#12 - eliminate need for separate require 'pry-nav', closes #9

Pull Request - State: closed - Opened by banister over 12 years ago - 1 comment

#11 - 'next' steps into Pry code after done with app code

Issue - State: closed - Opened by sent-hil over 12 years ago - 2 comments

#10 - pry-nav is having problems with pry-remote

Issue - State: closed - Opened by mrinterweb over 12 years ago - 7 comments

#9 - Sadness

Issue - State: closed - Opened by trans over 12 years ago - 5 comments

#8 - Segmentation fault

Issue - State: open - Opened by ylluminate over 12 years ago - 18 comments

#7 - prevent pry-nav turning on the tracer for non-bindings

Pull Request - State: closed - Opened by banister over 12 years ago - 1 comment

#6 - Support 1.8.7

Pull Request - State: closed - Opened by ConradIrwin over 12 years ago - 5 comments

GitHub / nixme/pry-nav issues and pull requests