From: Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Tab completion in BASH 2.04
Date: Sun, 18 Mar 2001 22:20:04 +0000
Lines: 27
Message-ID: <q1dabt4l7ec0a0jted3rpvt56ch0g34ebg@4ax.com>
NNTP-Posting-Host: modem-222.california.dialup.pol.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news8.svr.pol.co.uk 984953957 1888 62.137.56.222 (18 Mar 2001 22:19:17 GMT)
NNTP-Posting-Date: 18 Mar 2001 22:19:17 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Newsreader: Forte Agent 1.7/32.534
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Unfortunately, I think I have found a bug in BASH 2.04 tab completion.

Tab completion works fine, even with spaces in the name, unless the
path starts with a dos style drive name.  DJGPP port of BASH 2.03 does
not have this problem:

bash-2.03$ cd c:/
bash-2.03$ mkdir "foo bar"
bash-2.03$ rmdir c:/foo

 press TAB

bash-2.03$ rmdir c\:/foo\ bar/
bash-2.03$

...

bash-2.04$ cd c:/
bash-2.04$ mkdir "foo bar"
bash-2.04$ rmdir c:/foo

 press TAB

bash-2.04$ rmdir c:/foo bar/

The directory is obviously found ok, but the colon and space have not
been escaped.