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
To:	cygwin AT cygwin DOT com
From:	Robert R Schneck <schneck AT math DOT berkeley DOT edu>
Subject:	Re: rxvt/bash tab problem
Date:	Fri, 16 Jul 2004 02:16:16 +0000 (UTC)
Lines:	14
Message-ID:	<cd7dpf$sb7$1@sea.gmane.org>
References:	<20040716000318 DOT 5E12A84C87 AT pessard DOT research DOT canon DOT com DOT au>
X-Complaints-To:	usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	206-15-137-176.dialup.ziplink.net
User-Agent:	slrn/0.9.8.0 (CYGWIN_NT-5.1)

luke DOT kendall AT cisra DOT canon DOT com DOT au wrote:
> 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.

Putting 
shopt -s no_empty_cmd_completion
in your .bash_profile is a good way to avoid this.

I don't know what's up with your other comment about weird interaction 
between multiple presses of TAB and CTRL-C, but I would tend to guess 
it's not a Cygwin issue.

Robert


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