8000 No keyboard output when debugging · Issue #897 · guard/guard · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

No keyboard output when debugg 8000 ing #897

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
tomrossi7 opened this issue Feb 1, 2018 · 6 comments
Open

No keyboard output when debugging #897

tomrossi7 opened this issue Feb 1, 2018 · 6 comments

Comments

@tomrossi7
Copy link

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
Copy link
Author

Is anyone maintaining this or am I the only one seeing this issue?

@bmulholland
Copy link

I'm encountering it as well

@lluis
Copy link
lluis commented Apr 9, 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!

@tomrossi7
Copy link
Author

Thanks @lluis !

@travisp
Copy link
travisp commented Feb 3, 2020

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

@bkazez
Copy link
bkazez commented Apr 23, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@bkazez @tomrossi7 @lluis @travisp @bmulholland
0