X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: bash 3.x path completion problems
Date:	Tue, 30 May 2006 17:51:28 +0100
Message-ID:	<032301c68409$4bef3da0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<83c75fec0605300940s4bb1363s5aa58d8b42e195c3@mail.gmail.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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id k4UGpeCU027316

On 30 May 2006 17:40, burning shadow wrote:

> Since version 3 bash has problems with path completion. 

  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.

> For example,
> here's directory listing:
> 
> shadow:~/tmp$ ls -la
> total 1
> drwxr-xr-x+  4 shadow None   0 May 30 20:41 .
> drwxr-xr-x+ 10 shadow root   0 May 29 20:34 ..
> drwxr-xr-x+  8 shadow None   0 Apr 26 22:16 games
> drwxr-xr-x+  5 shadow None   0 May 30 20:42 qqq
> -rwx------   1 shadow None 208 Apr  6 20:04 s
> 
> shadow:~/tmp$ ls -la qqq
> total 1
> drwxr-xr-x+ 5 shadow None  0 May 30 20:42 .
> drwxr-xr-x+ 4 shadow None  0 May 30 20:41 ..
> drwxr-xr-x+ 2 shadow None  0 May 30 20:41 162567asd
> -rw-r--r--  1 shadow None 12 May 30 20:42 qqq.txtx
> drwxr-xr-x+ 2 shadow None  0 May 30 20:41 qwter
> drwxr-xr-x+ 2 shadow None  0 May 30 20:42 wqyteuqt
> shadow:~/tmp$
> 
> Now I'm entering "cd q" and pressing Tab 1 time. I get what I expected:
> 
> shadow:~/tmp$ cd qqq/
> 
> Now I'm pressing Tab 2 times and get this:
> 
> shadow:~/tmp$ cd qqq/
> 162567asd/ qqq.txtx   qwter/     wqyteuqt/
> shadow:~/tmp$ cd qqq/qq/
> 
> The problem is that 'qqq/qq/' thing. This was never happened to bash 2.05b.

  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?

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

dk AT rainbow /tmp/try_it> ls -la
total 0
drwxr-xr-x+ 4 dk Domain Users 0 May 30 17:42 .
drwxrwxrwt+ 4 dk Users        0 May 30 17:42 ..
drwxr-xr-x+ 2 dk Domain Users 0 May 30 17:42 games
drwxr-xr-x+ 5 dk Domain Users 0 May 30 17:49 qqq
-rwx------  1 dk Domain Users 0 May 30 17:42 s
dk AT rainbow /tmp/try_it> ls -la qqq/
total 0
drwxr-xr-x+ 5 dk Domain Users 0 May 30 17:49 .
drwxr-xr-x+ 4 dk Domain Users 0 May 30 17:42 ..
drwxr-xr-x+ 2 dk Domain Users 0 May 30 17:49 162567asd
-rw-r--r--  1 dk Domain Users 0 May 30 17:43 qqq.txtx
drwxr-xr-x+ 2 dk Domain Users 0 May 30 17:49 qwter
drwxr-xr-x+ 2 dk Domain Users 0 May 30 17:49 wqyteuqt
dk AT rainbow /tmp/try_it> cd qqq/
162567asd/ qqq.txtx   qwter/     wqyteuqt/
dk AT rainbow /tmp/try_it> cd qqq/


    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/

- Raw text -