guard: Typing doesn't appear in terminal after exiting guard
I’ve been running into this strange behavior for a while. I’ll exit guard with ctrl+D and when I get a bash prompt, nothing appears at the prompt when I type. I can type shell commands and they will execute, but no text appears as I type. The output from the commands typed does show up. Using GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu).
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 23 (10 by maintainers)
Commits related to this issue
- get readline support (ctrl+r etc) for Pry in OSX See https://github.com/guard/guard/issues/619#issuecomment-71212249 Technically for OSX you don't need readline, and we'll focus on using libedit whi... — committed to bf4/dotfiles by bf4 9 years ago
- get readline support (ctrl+r etc) for Pry in OSX See https://github.com/guard/guard/issues/619#issuecomment-71212249 Technically for OSX you don't need readline, and we'll focus on using libedit whi... — committed to bf4/dotfiles by bf4 9 years ago
in the meantime, have you tried typing
reset?(I found this issue because when I’m running guard with pry-byebug, I can see what I type in my guard repl, but when I add a binding.pry to a file, I can’t see what I’m typing in the that repl. Weird