Broken auto-completion in bash
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bash-completion (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: bash-completion
The autocompletion behaviour of bash is strange when I install a fresh Ubuntu with an encrypted home directory. Here's an example (I use underscore _ here to show where the cursor is - there is NO underscore in the actual file names in these examples.)
user@machine:~$ ls MyF_<TAB>
completes to:
user@machine:~$ ls MyFolder _
with a space behind the folder name instead of a slash. Actually I was expecting it to go like:
user@machine:~$ ls MyF_<TAB>
user@machine:~$ ls MyFolder/_<TAB>
MyFolder/
MyFolder/
Another annoyance is the handling of spaces.
user@machine:~$ ls -1_<ENTER>
My Folder With Spaces
user@machine:~$ ls My_<TAB>
user@machine:~$ ls My Folder With Spaces _
user@machine:~$ ls My\ _<TAB>
user@machine:~$ ls My Folder With Spaces _
user@machine:~$ ls "My _<TAB>
user@machine:~$ ls My Folder With Spaces _
This is really annoying. Deleting the .bashrc didn't help, I didn't find anything related in it anyway. Thanks for any help. This occurs only with some commands: cd seems to work fine, but cat, ls or rm show the same behaviour.
| Johann Philipp Strathausen (strathausen) wrote | #1 |
| summary: |
- Broken auto-completion in bash when home-directory is encrypted + Broken auto-completion in bash |
| Johann Philipp Strathausen (strathausen) wrote | #2 |
| Marcel Stimberg (marcelstimberg) wrote | #3 |
| Changed in bash-completion (Ubuntu): | |
| status: | New → Confirmed |
I'm not even sure anymore it is related to the encrypted directory thing at all (although I've noticed bash behaving completion differently on mounted directories). Tried it with a differend user with an unencrypted home, same problems.
The steps I did to get here:
1. install fresh Ubuntu Natty 64bit
2. install some packages I usually use (see attachment #1)
So, my work-around is to use zsh instead, and I like it so much I don't think I'll use bash anymore. But I am still curious about this bug, any hint on this is appreciated.