Andy Rusterholz

+1

+1, please release this.

+1. This is one of the most obnoxious issues with any development tool I've ever tried (and I've been developing since the TRS-80 came out, if that gives you a...

Any updates on this?

This is still easily reproduced with ruby 2.3.1 and pry 0.10.4: ``` Cedar:blinker rusterholz$ irb 2.3.1 :001 > require 'pry' => true 2.3.1 :002 > puts 'one' one => nil...

+1. Ctrl-C while in a Pry session totally kills echo. Not using Spring or Foreman. `reset` and `stty echo` have no apparent effect. I can't in good conscience recommend that...

Any update on this issue from the developers?

@banister I'm over a year late responding to your question, but this is still very easy to reproduce: Step 1: Have a project with ruby 2.3.1, rspec 3.5.0, and pry...

Sure! I will also update my original description with this info: 1. This occurs in Ruby files (.rb suffix). I am just using the built-in Ruby support in Sublime Text...

Two other things I've also noticed during my testing today: 1. Sometimes **no** error message appears on the console -- that is, sometimes this failure is totally silent. At any...