autocomplete doesn't work properly on file :0.log when bash-completion is installed

[scop]

https://bugzilla.redhat.com/show_bug.cgi?id=962492

Andre Robatino 2013-05-13 12:27:45 EDT
Description of problem:
I have a file named :0.log (one of the gdm logs). If I try to use ls -l on it by typing : and then tabbing to autocomplete, I get

[andre@compaq-pc tmp]$ ls -l :\:0.log 
ls: cannot access ::0.log: No such file or directory
[andre@compaq-pc tmp]$

If instead I first type \: and then autocomplete, it works. If I uninstall bash-completion and open a new terminal, then typing : and tabbing gives me a list of possibilities including the correct one.

Version-Release number of selected component (if applicable):
bash-completion-2.1-2.fc18.noarch

How reproducible:
always

[reply] [−] Comment 1 Ville Skyttä 2013-05-14 10:36:42 EDT
That would be entry E13 in the bash FAQ: http://tiswww.case.edu/php/chet/bash/FAQ, and see also __ltrim_colon_completions comments in /usr/share/bash-completion/bash_completion

I suppose we should consider doing the COMP_WORDBREAKS modification in the bash-completion package automatically, for example in /etc/profile.d/bash_completion.sh

[jarnos]

Apparently backslashes have disappeared in the post.

[scop]

Not sure if they've ever been there. Nevertheless I think it's readable enough.

[jarnos]

Well, they should have, but GitHub removes them even if you did type them unless you type double backslashes. I suppose you meant

If instead I first type \: and then autocomplete, it works.

[scop]

Ah, back_slashes_! I somehow read that as backticks. Anyway, fixed now using backticks :)

[kevinoid]

I just encountered this issue (I think) for directories which contain a colon. An example:

mkdir -p /tmp/test:dir/testdir
ls /tmp/test:dir/<tab>   # Does not complete
ls /tmp/test\:dir/<tab>  # Completes to /tmp/test\:dir/testdir/

This can be problematic in /sys where LED, PCI, and several other common device paths contain colons.