From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.1) Gecko/20020815
Description of problem:
Since a short while bash directory completion is broken, it doesn't attach the /
at the end anymore.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. # cd /usr
2. # ./bi<TAB>
Actual Results: This will give you:
"# ./bin "
Expected Results: I expect (and it was this way until recently):
This "feature" was introduced in bash-2.05b-alpha1.
i. Fixed the command name completion code so a slash is no longer appended
to a single match if there happens to be a directory with that name in
I hope this will be reverted.
Ah, this brought me on the right track, somehow I thought this was a RH specific
bug, but it is generic. Searching Google revealed this patch on the bug-bash list:
I tried it and it works fine for me.
Should be fixed in bash-2.05b-6.
*** Bug 76869 has been marked as a duplicate of this bug. ***
*** Bug 77535 has been marked as a duplicate of this bug. ***
If you used the patch Franz pointed to, this will still be broken. Thanks to
Paul Jarc <email@example.com>:
Derek Robert Price <firstname.lastname@example.org> wrote:
> Tab completion now inserts spaces after directory names rather than slashes
> to allow for further path specification.
> Was this an intentional change or a bug?
It's a bug, partially fixed by patch bash205b-003. This patch fixes
cases that start with "~", ".", or "/". Other cases, like
foo/bar<TAB> without a leading "./", still get a space appended.
*** Bug 77796 has been marked as a duplicate of this bug. ***
*** Bug 78037 has been marked as a duplicate of this bug. ***
Still bronken in Phoebe.
Please try 2.05b-16, which will shortly appear in rawhide.
*** Bug 84058 has been marked as a duplicate of this bug. ***
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.
I wonder why this bug is closed, if one variant of it (see comment #6)
is still present (at least in 2.05b-r9)
In 3.00.16 it seems to be fixed.