In my Rails application I am using the following gems for guard debugging:
guard 2.14.2
guard-minitest 2.4.6
byebug 10.0.0
The problem is that when I drop into a debugger I don't see any output when I type. The commands work, but I'm blind to what I am typing. Can someone point me in the right direction? Is this a Guard issue?
Incidentally, I am able to resolve the issue by downgrading:
guard 2.6.1
guard-minitest 2.3.2
tomrossi7
All 6 comments
Is anyone maintaining this or am I the only one seeing this issue?
tomrossi7
on 12 Mar 2018
I'm encountering it as well
bmulholland
on 12 Mar 2018
do you have rb-readline gem installed?
In my case (I had rb-readline 0.5.4) removing it from Gemfile solved this issue!
lluis
on 9 Apr 2018
Thanks @lluis !
tomrossi7
on 9 Apr 2018
do you have rb-readline gem installed?
In my case (I had rb-readline 0.5.4) removing it from Gemfile solved this issue!
This doesn't seem to be a solution, since rb-readline is suggested by the gem to work properly on MacOS
travisp
on 3 Feb 2020
I am having this issue with pure byebug. Makes it very annoying to debug. Related SO post: https://stackoverflow.com/questions/63492596/why-cant-i-type-in-terminal-after-hitting-binding-pry-or-byebug-when-running-ra
bkazez
on 23 Apr 2021
Related issues
bgentry
·
10Comments
greyblake
·
18Comments
thibaudgg
·
3Comments
jonmchan
·
16Comments
lastobelus
·
5Comments
Most helpful comment
do you have rb-readline gem installed?
In my case (I had rb-readline 0.5.4) removing it from Gemfile solved this issue!