From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.7.6)
Description of problem:
The bash auto-completion mecanism has changed from RHEL3 to RHEL4. Bug #116135
describes the problem. Sometimes, hitting TAB is not enough to obtain
auto-completion. You need to press another key before completion is displayed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. find some folder with files which do have common prefix
2. type a shorter prefix of that prefix
3. press tab - nothing happens
4. press any key - word is completed
Actual Results: bash auto-completion doesn't work as well as the version
shipped with RHEL3.
Expected Results: bash auto-completion should always be done at step #3.
Bug #116135 states that this is the expected behavior. How do I get back to the
The behaviour has certainly not changed intentionally between Red Hat Enterprise
Linux 3 and 4, and the "steps to reproduce" you list above are confusing to me
-- were they copied from the bug report you reference? Incidentally, that bug
report used the base version of bash that shipped in Red Hat Enterprise Linux 3,
which also indicates that this is not a regression from that product.
I have never seen the failure mode you describe, myself. Is is really correct
that you press a key other than tab and suddenly (without again pressing tab)
the word is completed? That would indeed be a bug.
What I get with a clean installation of Red Hat Enterprise Linux 4, following
your "steps to reproduce", is this:
3. The full common prefix is completed
4. The key I typed (x) appears after the common prefix.
My RHEL4 installation is not "clean". The system was upgraded from a RHEL3
system with yum (which is not the recommended way, I know). I will try to
reproduce this behavior with a clean install.
After some verifications, I found this bug is specific to the konsole program. I
was not able to reproduce it under gnome-console and xterm. Bug #155818 was
filled which describes a way to reproduce the problem.
*** This bug has been marked as a duplicate of 155818 ***