X-Spam-Check-By:	sourceware.org
Message-ID:	<83c75fec0605301007n57fbcd80x2e828e10dda436ed@mail.gmail.com>
Date:	Tue, 30 May 2006 21:07:40 +0400
From:	"burning shadow" <burning DOT shadow AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: bash 3.x path completion problems
In-Reply-To:	<83c75fec0605300940s4bb1363s5aa58d8b42e195c3@mail.gmail.com>
MIME-Version:	1.0
References:	<83c75fec0605300940s4bb1363s5aa58d8b42e195c3 AT mail DOT gmail DOT com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

>   Since version 3, bash has had problems with readline causing spurious 'ghost'
> characters to echo to the screen, particularly when scrolling through the history
> buffer or using a prompt with non-printing chars in it.  It may affect completion too.

Is there any solution?

>   The real question is whether the trailing 'qq/' is actually there in the input buffer or if it's
> just an optical illusion caused by the readline bug.  What happens if you immediately
> press enter?

It's an 'illusion', but it makes it very hard to navigate thru directories.

>   BTW with all the latest updates (including cygwin dll from cvs, but that's probably not
> relevant) I can't reproduce your example:

I don't have CVS version of the DLL, but I have updated all packages
before making bug report..

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