Problem with bash completion
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bash (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Binary package hint: bash
see http://
this happens to me (and i'm pretty sure that in a different scenario than the one described below) and is very annoying. can you please update the bash package to the one where this bug doesn't happen?
from the thread:
From: David Rothenberger
Subject: Problem with bash completion
Sometimes bash gets confused and starts adding a slash at the end of
files when I do tab-completion. Here's a simple reproduction script:
~ > bash --noprofile --norc -i
bash-3.2$ mkdir /tmp/bash-problem
bash-3.2$ cd /tmp/bash-problem
bash-3.2$ mkdir d
bash-3.2$ touch x
bash-3.2$ chmod 755 x
bash-3.2$ ./x <---- tab after x completes correctly
bash-3.2$ ./d/ <---- ditto with d
bash: ./d/: is a directory
bash-3.2$ "$(ls ./d/)" <---- pressed tab after d
bash: : command not found
bash-3.2$ ./x/ <---- tab after x now adds slash
Once the shell starts doing this, it keeps doing it. Restarting bash
solves the problem.
I have the same problem here. The (non-deterministic) steps to reproduce are:
1. Start bash ename[TAB] ename[TAB] again
2. cat someprefixoffil
3. The name is completed correctly
4. Work
5. cat someprefixoffil
6. This time, the filename comes with a slash "/" in the end
7. (obviously) cat gives an error saying that the directory was not found