I see the same behaviour as posted above. # mkdir =foo =foobar # cd =\=foo -bash: cd: ==foo: No such file or directory # echo $BASH_VERSION 2.05b.0(1)-release
I get the same result with bash version 3.00.15(1)-release. I am not sure if this is related to bash completion package. Also this maynot be a bug as bash might be treating '=' as a word break character. Kalyan On 7/7/05, Chet Ramey <[EMAIL PROTECTED]> wrote: > > Machine Type: i586-mandrake-linux-gnu > > > > Bash Version: 2.05b > > Patch Level: 0 > > Release Status: release > > > > Description: > > [Hello, whenever I hit tab to have completion on a directory whose > > name start by = i got that : > > > > cd =\=Boulot > > bash: cd: ==Boulot: No such file or director] > > This is a problem with whatever completion function you have defined for > `cd'. It's probably from /etc/bash_completion or something similar; see > if there's a bug reporting address there (it's probably [EMAIL PROTECTED]). > > Chet > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ( ``Discere est Dolere'' -- chet ) > Live...Laugh...Love > Chet Ramey, ITS, CWRU [EMAIL PROTECTED] > http://tiswww.tis.case.edu/~chet/ > > > _______________________________________________ > Bug-bash mailing list > Bug-bash@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-bash > _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
