X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
Subject: RE: bash 3.x path completion problems
Date: Tue, 30 May 2006 18:21:28 +0100
Message-ID: <032401c6840d$7c72d6e0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="UTF-8"
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <83c75fec0605301007n57fbcd80x2e828e10dda436ed@mail.gmail.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k4UHLfEK031362

On 30 May 2006 18:08, burning shadow wrote:

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

  I don't know.  Like all bugs, it of course /can/ be fixed; whether it has been or not in upstream is another question.
 
>>   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.

  Yeh, I find it horribly distracting too.
 
>>   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..

  Like I said, it's unlikely that this is the thing that makes the difference, but you could always have a quick try with the latest snapshot just in case:
http://cygwin.com/snapshots.  It might also be trying the different cygwin terminals, xterm and rxvt as well as plain old dos console.



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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