delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/07/15/20:03:29

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:03:18 +1000 (EST)
From: luke DOT kendall AT cisra DOT canon DOT com DOT au
Subject: rxvt/bash tab problem
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Message-Id: <20040716000318.5E12A84C87@pessard.research.canon.com.au>

If at a fresh bash prompt in an rxvt window (non-X) you type a TAB,
nothing happens, and no input from the keyboard appears thereafter,
until you use CTRL-C to interrupt whatever has blocked.

If you then type, input is working again.

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.

Windows XP SP1; cygwin 1.5.10.

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 -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019