X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Wed, 8 Dec 2010 12:28:43 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: unable to type command into Cygwin after running 'tail'
Message-ID: <20101208172843.GD21011@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
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> <AANLkTi=wA08KmvHj1GmQYL2btTC_UMNyr_2vo-n_h8PA@mail.gmail.com> <251BBCD7-370F-42F1-8305-01F9E6F87D1E@nozzala.net> <AANLkTikJA3HZEOtjnoKJfZOA7pYRJoePgFJXQtezCkFU@mail.gmail.com> <loom.20101208T163434-656@post.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <loom.20101208T163434-656@post.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
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 Wed, Dec 08, 2010 at 04:06:35PM +0000, TJ Anthony wrote:
>Andy Koppe <andy.koppe <at> gmail.com> writes:
>
>> 
>> 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.
>> 
>> Andy
>> 
>> 
>
>Fresh shell:
>
>speed 38400 baud; line = 0;
>start = <undef>; stop = <undef>;
>-imaxbel
>-echoe -echok -echoctl -echoke
>
>After ctrl+C during a grep which is redirecting output to a file:
>
>$ speed 38400 baud; line = 0;
>start = <undef>; stop = <undef>; lnext = <undef>; min = 1; time = 0;
>-icrnl -imaxbel
>-icanon -echo -echoe -echok -echoctl -echoke

Can anyone duplicate this problem with a non-bash shell?

cgf

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