[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug/Request for change - in filename completion behaviour on windows p
Bug/Request for change - in filename completion behaviour on windows platform
Wed, 13 Mar 2002 15:45:40 +0100
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1
Configuration Information [Automatically generated, do not change]:
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
Machine Type: i686-pc-cygwin
Bash Version: 2.05a
Patch Level: 0
Release Status: release
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
but I am used to give pathnames the other way.
So, I'd like to have this changed, or at least customizable.
-> The filename completion will not work.
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 Roeder E-mail: address@hidden
CoCreate Software GmbH FAX: 07031-951-2320
Posener Str. 1
- Bug/Request for change - in filename completion behaviour on windows platform,
Roland Roeder <=