minor bash completion bug for files containing an equal sign

[Nico Dietrich]

Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' 
-DSHELL -DHAVE_CONFIG_H  -I.  -I../bash -I../bash/include -I../bash/lib 
  -g -O2
uname output: Linux karl 2.6.9 #2 Tue Oct 26 19:49:30 CEST 2004 i686 
GNU/Linux
Machine Type: i386-pc-linux-gnu

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


Description:

	Bash completes to files or directories that don't exist. This problem 
occurs only because of non-escaping the equal sign. But since bash 
allows this, it's still a bug.


Repeat-By:

        Situation 1:

        $ mkdir =
        $ cd =[TAB]  produces  $ cd =\=/

	Problem: Bash completes to '==', which doesn't exist. It should only 
replace '=' by '\='.

        
        Situation 2:

        $ mkdir foo
        $ touch foo/bar=
        $ vi foo/bar=[TAB]  completes to  $ vi foo/bar=foo/bar\=
        
	Problem: as above - bash completes to something that doens't exist, 
should only replace '=' by '\='



--
Nicolas Dietrich
http://omnibus.uni-freiburg.de/~dietricn