rking / pry-plus

Pry plus the essential plugins.

pry-plus

Get up and going with a good set of pry tools right away.

Dependent Gems

pry-doc

Allows you to look into the Ruby builtin classes with the ? and $ commands.

• ? [].pop

• $ [].pop

• …etc.

pry-docmore

Shows docs for dollar-vars and keywords

• show-docmores

• ? module

• ? $`

pry-debugger

An essential gem. Turns Pry into a steppable debugger.

• Making the basic "require'pry';binding.pry" from a script come alive.

• In conjunction with plymouth or pry-rescue, to explore failing tests.

• Following calls into other libs.

pry-stack_explorer

Allows you to navigate the call stack.

• So many. TODO = document some.

pry-exception_explorer

Somewhat of a competitor to pry-rescue, but implemented differently. Currently doesn't work on C exceptions (such as 1/0 errors).

• Let an exception happen in the REPL, then use enter-exception to find it.

• Inline-style trap

• Block wrapper-style trap

• http://vimeo.com/36061298 ← "mini screencast"

pry-rescue

Provides Pry.rescue do … end to capture any exceptions and start pry from the context of the source of the exception.

• Shortens write-run-debug cycles when exceptions are involved.

• Exploring causes of hard-to-replicate exceptions.

• Rescues on test failure via require of pry-rescue/minitest and pry-rescue/rspec

bond

An excellent tabcompletion gem. Having this dep enables new Pry stuff. Note that pry v0.9.10 doesn't have this feature, so you must use a repo version.

• require 'x<tab>

• {asdf: 1, hjkl: 2}[:a<tab>

• Chain.of.calls.<tab> # Old pry completion was generic in this case.

jist

Replacement for the undermaintained gist gem.

• Improved implementation for Pry's gist command.

• Check out the jist -h output on the CLI, by the way.

pry-plus's Issues

get all underlying gems

i would like to simply require 'pry-plus' and have all of the underlying gems automatically required for me.

Broken Pry

Just installed your gem and now I get this error every time I try to start pry:

/Users/jhn/.rvm/gems/ruby-1.9.3-p194@rails327/bin/ruby_noexec_wrapper:14: stack level too deep (SystemStackError)

I'm using this custom .pryrc.

pry and pry-plus in production

Hello.
I'd like to have rails console using pry in RAILS_ENV=production too.

but if I have following in Gemfile

gem 'pry-rails'
gem 'pry-plus', group: :development

then all the deps are loaded too, even in unicorn instances. My particular problem is with pry-rescue, intercepting SIGQUIT, and that's messes up with unicorn reloading.

Do you think it's possible to load pry-plus deps only when actually starting rails console?

Segmentation fault with Pry-Plus when called through RSpec

I'm running into a Segmentation fault inconsistently when a add binding.pry to my spec file. What's strange is that it sometimes works, this error is intermittent. The specific error is:

/home/vagrant/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/gems/1.9.1/gems/pry-stack_explorer-0.4.9.1/lib/pry-stack_explorer/when_started_hook.rb:6: [BUG] Segmentation fault
ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-linux]

I have pry-plus and rspec-core 3.0.0.beta1 in my gemfile
pry -v = Pry version 0.9.12.4 on Ruby 1.9.3
ruby -v = ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-linux]

I'm running my ruby dev on a Linux 10.04.4 Virtualbox called from a Vagrantfile.
Thanks for the help!

pry-debugger 'next' has bugs replace with pry-byebug

Hi,

I am using pry-plus with ruby 2.0 and I occasionally hit an issue where 'next' works like step, see this issue nixme/pry-debugger#34. The recommendation is to use pry-byebug instead. If install pry-byebug with pry-plus will I have issues or will I need to install everything separately?

Thanks,
Jay

Come back!

RKing! We need you to update this!