Bash completion buggy if -o nospace, -o filenames and -W used together.

[Christian Boltz]

Hello,

I've found a bug in bash autocompletion...


Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux
Compiler: gcc -I/usr/src/packages/BUILD/bash-3.0 
-L/usr/src/packages/BUILD/bash-3.0/../readline-5.0
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' 
-DCONF_OSTYPE='linux' -DCONF_MACHTYPE='i586-suse-linux' 
-DCONF_VENDOR='suse' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' 
-DSHELL -DHAVE_CONFIG_H  -I.  -I. -I./include -I./lib   -O2 -march=i586 
-mcpu=i686 -fmessage-length=0 -Wall -g -D_GNU_SOURCE -Wall -pipe -g 
-fbranch-probabilities
uname output: Linux cboltz 2.6.11.4-21.7-default #1 Thu Jun 2 14:23:14 
UTC 2005 i686 i686 i386 GNU/Linux
Machine Type: i586-suse-linux

Bash Version: 3.0
Patch Level: 16
Release Status: release

Description:
    Bash completion is buggy if -o nospace, -o filenames and -W are
    used together. See the commented example below.

    If you let one of the options away, the problem doesn't occour.
    Also -o dirnames instead of -o filenames works well.

Repeat-By:

("<tab>" means pressing the "tab" key)
# complete -d -o nospace -o filenames -W '--foo=' foo
# foo <tab><tab>
dir1/     dir2/  --foo=
# foo --f<tab><tab>       # results in "--foo\="
# foo --foo\=<tab><tab>   # <-- why does this backslash appear?
--foo=                    #     It prevents dirname autocompletion :-(
# foo --foo=<tab><tab>    # <-- manually removed the backslash,
dir1/     dir2/  --foo=   #     now it works :-)


It would be nice if you could fix that problem ;-)


Regards,

Christian Boltz
-- 
2.-5.9.2005: Weinfest in Insheim
Bei der Landjugend: Liquid, AH-Band und Deafen Goblins
Mehr Infos: www.Landjugend-Insheim.de