rxvt/bash tab problem

luke.kendall@cisra.canon.com.au luke.kendall@cisra.canon.com.au
Fri Jul 16 01:24:00 GMT 2004

On 16 Jul, To: cygwin@cygwin.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

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


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/

More information about the Cygwin mailing list