X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4CF7E822.2050705@cwilson.fastmail.fm>
References: <30355317.post@talk.nabble.com>	<4CF70A11.8020604@acm.org>	<76B81B8B64B6254B98733990F38621DA6A77@sron-chi-exc05.ronin.roncap.com>	<4CF7E501.9080901@acm.org>	<4CF7E822.2050705@cwilson.fastmail.fm>
Date: Thu, 2 Dec 2010 19:59:05 +0000
Message-ID: <AANLkTi=wA08KmvHj1GmQYL2btTC_UMNyr_2vo-n_h8PA@mail.gmail.com>
Subject: Re: unable to type command into Cygwin after running 'tail'
From: Andy Koppe <andy.koppe@gmail.com>
To: Charles Wilson <cygwin@cwilson.fastmail.fm>, cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

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

