pry-exception_explorer icon indicating copy to clipboard operation
pry-exception_explorer copied to clipboard

Enter the context of exceptions

Results 13 pry-exception_explorer issues
Sort by recently updated
recently updated
newest added

Without `pry-exception_explorer`. ``` ~[master]% cat dir cat: dir: Is a directory ~[master]% pry [1] pry(main)> cat dir Errno::EISDIR: Is a directory - /home/curacao/dir from /home/curacao/.gem/ruby/1.9.1/gems/pry-0.9.10/lib/pry/code.rb:131:in `each ' [2] pry(main)> ```...

bug

we dont need it now that exceptions are always configured for `enter-exception` to work inside the REPL

refactor

``` # Internal exceptions (C exceptions) are not intercepted inline (when EE.inline == true) by default. # This is because a fuck-tonne of internal exceptions are raised (but then rescued)...

documentation

The README doesn't mention that you have to first `require 'pry'` (and why is this, anyway? You're already severely punishing users by requiring them to type out this huge gem...

``` ruby require 'pry' require 'pry-exception_explorer' EE.enable! raise "hi" ``` results in ``` crow:projects john$ ruby v.rb Frame number: 0/19 Frame type: block From: /Users/john/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb @ line 63 Kernel#require: Frame...

bug

- must use `toggle-color` otherwise coderay causes infiniloop - even after toggling color, still doenst work very well - possibly due to hardcoding `START_FRAME_OFFSET = 6` in `lazy_frame.rb`

bug

should be able to do a remote session rather than a local system

feature