unable to type command into Cygwin after running 'tail'

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

On 2 December 2010 20:28, Heath Kehoe wrote:
>> FWIW, I can't reproduce this, even if I kill the tail or less with
>> SIGKILL, thus giving them no chance to do any cleanup. (I assume you
>> use 'less -K' to allow it to be ctrl-c'ed?)
>> Which shell do people who've seen the problem use? Is it an intermittent issue?
> If you SIGKILL a 'less' while it has the tty set for raw/noecho then the tty will stay in that mode.

Wel, yes, that was the point of trying that. The terminal settings
didn't get corrupted that way though, which suggests that it isn't
'less' that messes things up.

> 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)

Yep, a look at their sources confirms that.

> so if the tty is ending up with echo disabled,
> it's got to be the shell leaving it that way.

But then how did it get disabled in the first place?

> 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.

Agreed. Also, for anyone who sees the issue again, blindly typing just
'stty' (without the 'sane') and posting the output here might provide
a clue.


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