plymouth
plymouth copied to clipboard
banister
Start Pry in the context of a failed test
When setting up Plymouth for a project (working on a repro via failing test on [mdub/clamp](https://github.com/mdub/clamp)), I'm seeing the following exception: ``` .../.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/pry-stack_explorer-0.4.9/lib/pry-stack_explorer/commands.rb:133:in `': uninitialized constant PryStackExplorer::Pry (NameError) from /Users/whitley/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/pry-stack_explorer-0.4.9/lib/pry-stack_explorer/commands.rb:1:in...
be guard... ``` backtrace 10:59:52 - INFO - Running all specs /Users/kwerle/.rvm/gems/ruby-2.0.0-p0/gems/pry-exception_explorer-0.1.9/lib/pry-exception_explorer/core_ext.rb:91:in `raise': undefined method `callcc' for # (NoMethodError) from /Users/kwerle/.rvm/gems/ruby-2.0.0-p0/gems/activesupport-4.0.0.rc1/lib/active_support/dependencies.rb:217:in `rescue in load_dependency' from /Users/kwerle/.rvm/gems/ruby-2.0.0-p0/gems/activesupport-4.0.0.rc1/lib/active_support/dependencies.rb:210:in `load_dependency' from /Users/kwerle/.rvm/gems/ruby-2.0.0-p0/gems/activesupport-4.0.0.rc1/lib/active_support/dependencies.rb:228:in `require'...
I've put a failing test on https://github.com/rapportive-oss/em-imap.git (branch temp/plymouth-bug) which demonstrates this problem. Exceptions raised from code being tested are caught fine.
`Plymouth.disable!` The primary issue is what to do about plymouth in CI situations, it cant be kept on by default as it would hang travis on failure
I can't imagine when you'd want it. All it does for me is get in the way of tabcompletion for `plymouth-off`
I know this is probably annoying as it is probably due to a combination of things, but i'd rather tell you about it than not. When i added to my...
