This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: unable to type command into Cygwin after running 'tail'


On 2 December 2010 18:40, Charles Wilson wrote:
> On 12/2/2010 1:27 PM, David Rothenberger wrote:
>> Illia Bobyr wrote:
>>> On 12/1/2010 8:53 PM, David Rothenberger wrote:
>>>> Try typing "reset" or "stty sane" (without the quotes) and pressing
>>>> Enter. You won't see what you're typing, but after the shell should work
>>>> again.
>>>
>>> Would you, please, elaborate on this a little bit?
>>> Maybe a link or a reference that explains why this is happening?
>>
>> I'm sorry, I can't. I don't know why it is happening. I just know how to
>> recover from it as a user.
>
> I've noticed that this misbehavior occurs more frequently these days:
> ctrl-c'ing some tasks (tail, less, maybe a few others) ends up with the
> terminal settings all scrogged up

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?

Andy

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]