Bug/Request for change - in filename completion behaviour on windows platform

[Roland Roeder]

Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: cygwin
Compiler: i686-pc-cygwin-gcc
Compilation CFLAGS:  -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='
cygwin' -DCONF_MACHTYPE='i686-pc-cygwin' -DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFI
G_H   -I.  -I../bash-2.05a -I../bash-2.05a/include -I../bash-2.05a/lib -g -O2
uname output: CYGWIN_NT-5.0 D10PC474 1.3.9(0.51/3/2) 2002-01-21 12:48 i686 
unknown
Machine Type: i686-pc-cygwin

Bash Version: 2.05a
Patch Level: 0
Release Status: release

Description:
  The filename completion of bash doesn't work as I'd expect it. If the given
  filenames has the form '<drive_letter>:/<pathname>' bash seems to ignore the
  given drive and tries to complete the pathname starting from the root.
  Since all other programs in the cygwin toolset work fine with filenames
  containing drive specifiers I find this very inconsistent. I know that
  the filename completion works fine when using 
/cygdrive/<drive_letter>/<pathname>
  but I am used to give pathnames the other way.
  So, I'd like to have this changed, or at least customizable.

Repeat-By:
  start bash
  touch c:/foobar
  ls c:/foo<TAB>

  -> The filename completion will not work.

Fix:
  I have already found the place to be changed or to be made customizable.
  In bashline.c, line 193 and 194, there are the word break characters
  for the readline library defined. These characters contain the colon.
  By removing the colon from the list, I could change the behaviour.


Thanks for your help
  Roland

--
________________________________________________________________________

Roland Roeder                       E-mail: roland_roeder@cocreate.com
                                    Phone: 07031-951-2199
CoCreate Software GmbH              FAX:   07031-951-2320
Posener Str. 1
71065 Sindelfingen
Germany
________________________________________________________________________