unable to type command into Cygwin after running 'tail'

Andy Koppe andy.koppe@gmail.com
Fri Dec 3 13:05:00 GMT 2010

On 2 December 2010 20:49, Illia Bobyr wrote:
> On 12/2/2010 2:28 PM, Heath Kehoe wrote:
>> [...]
>> Also, the OP said the problem was happening on pipelines like 'tail | grep'. Neither tail nor grep muck with tty settings (that I know of), so if the tty is ending up with echo disabled, it's got to be the shell leaving it that way. Perhaps there's some kind of race condition in the shell's signal processing? So again, we'll need to know which shell this is happening with and a way to reliably repro the issue to have any hope of fixing it.
> Happens to me always if I grep a directory with a large binary files,
> grep is currently checking one of those huge files and I try to stop it
> by doing Ctrl+C.

How huge, and with what arguments to grep?

If it's actually printing binary data to the terminal, that's likely
to contain byte sequences that are meaningful to the terminal, thereby
messing up its state.


Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

More information about the Cygwin mailing list