X-Recipient:	archive-cygwin AT delorie DOT 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,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<76B81B8B64B6254B98733990F38621DA6A78@sron-chi-exc05.ronin.roncap.com>
References:	<30355317 DOT post AT talk DOT nabble DOT com> <4CF70A11 DOT 8020604 AT acm DOT org> <76B81B8B64B6254B98733990F38621DA6A77 AT sron-chi-exc05 DOT ronin DOT roncap DOT com> <4CF7E501 DOT 9080901 AT acm DOT org> <4CF7E822 DOT 2050705 AT cwilson DOT fastmail DOT fm> <AANLkTi=wA08KmvHj1GmQYL2btTC_UMNyr_2vo-n_h8PA AT mail DOT gmail DOT com> <251BBCD7-370F-42F1-8305-01F9E6F87D1E AT nozzala DOT net> <76B81B8B64B6254B98733990F38621DA6A78 AT sron-chi-exc05 DOT ronin DOT roncap DOT com>
Date:	Fri, 3 Dec 2010 13:05:02 +0000
Message-ID:	<AANLkTinTMwU4j5mfb3_Ms3EE8Q3Rv2p23=bxxzSvufge@mail.gmail.com>
Subject:	Re: unable to type command into Cygwin after running 'tail'
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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 | gr=
ep'. Neither tail nor grep muck with tty settings (that I know of), so if t=
he 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 signa=
l processing? So again, we'll need to know which shell this is happening wi=
th 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.

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

- Raw text -