FS#23846 - bash-completion partly broken

Attached to Project: Arch Linux
Opened by Andreas Gohr (splitbrain) - Tuesday, 19 April 2011, 20:08 GMT
Last edited by Eric Belanger (Snowman) - Thursday, 21 April 2011, 03:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Bash completion isn't working as expected/before. Variables are not handled correctly, sometime directories are not completed with a trailing slash.

bash-completion 1.3-2

Examples:

* Using 'mv /et<TAB>' produces 'mv /etc ' but should produce 'mv /etc/'. It works correct with 'ls'.
* Using 'ls $HO<TAB>' does nothing, but should complete to 'ls $HOME'.
* Using 'unzip $HOME/myfi<TAB>' produces 'unzip \$HOME/myfile.zip' but should produce 'unzip $HOME/myfile.zip'.
This task depends upon

Closed by  Eric Belanger (Snowman)
Thursday, 21 April 2011, 03:09 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#22807 
Comment by Greg (dolby) - Tuesday, 19 April 2011, 23:45 GMT
Please report this here: http://bash-completion.alioth.debian.org
Comment by Greg (dolby) - Tuesday, 19 April 2011, 23:47 GMT
Whats so different from  FS#22807  btw? It looks the same report and that one was closed.
Comment by Andreas Gohr (splitbrain) - Wednesday, 20 April 2011, 06:46 GMT
 FS#22807  only affected directory completion, but for any command. And as you said it was fixed, so this is a new bug.

But okay, I reported it here https://alioth.debian.org/tracker/index.php?func=detail&aid=313091&group_id=100114&atid=413095
Comment by Greg (dolby) - Wednesday, 20 April 2011, 10:54 GMT
I see that the above upstream report is closed now. Marked as the same bug as  FS#22807  ?
Comment by Andreas Gohr (splitbrain) - Wednesday, 20 April 2011, 11:12 GMT
I added a comment about this at the alioth system.
Comment by Andreas Gohr (splitbrain) - Wednesday, 20 April 2011, 19:40 GMT
I had some more time today and througly tested this.

Turns out that the $variable completion problem seems to be a problem in BASH itself and also happens without bash-completion installed at all. I found a thread about it here: https://bbs.archlinux.org/viewtopic.php?id=115548

The directory completion problem is created by acroread's 3rd party script (though I could have sworn it I ruled that out yesterday), so it seems really to be  FS#22807  again, but only affects certain commands like mv this time.

Sorry for the trouble, I think this bug can be closed.

Loading...