Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Fri, 16 Jul 2004 10:34:37 +1000 (EST)
From:	luke DOT kendall AT cisra DOT canon DOT com DOT au
Subject:	Re: rxvt/bash tab problem
To:	cygwin AT cygwin DOT com
In-Reply-To:	<20040716000318.5E12A84C87@pessard.research.canon.com.au>
MIME-Version:	1.0
Message-Id:	<20040716003437.0423084C87@pessard.research.canon.com.au>

On 16 Jul, To: cygwin AT cygwin DOT com wrote:
>  But if you hit TAB twice in quick succession, you'll find that no input 
>  appears (again), and that while you can use CTRL-C to get a fresh 
>  prompt, input no longer works in the rxvt window.  You have to kill the 
>  window - it has become useless. 

This is untrue.  I just discovered that if you wait long enough, the
input is echoed and the rxvt becomes normal again.

If you type another CTRL-C, you get a fresh prompt, but still no input
echoed.

If you hit CTRL-C *again*, then everything you typed gets passed
through to the shell and acted upon!

(I.e. the input hasn't been flushed by the CTRL-C, and there is some
process/thread that ignores the interrupt and refuses to echo the input
as it occurs.)

luke


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -