bash-completion needs match "fallback" function. (supported but upstream doc not packaged)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bash-completion (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bash-completion
It would make the most sense if I just given an example. Suppose I have a DVD .ISO file buried a couple levels down in my filesystem, that I want to open with XINE, and I type the following (knowing for certain it will resolve to exactly one match):
xine /ra{tab}
It would normally expand to something like:
xine /rainbird/
However, bash-completion prevents this match,probably because it thinks XINE can't play an ISO file. It of course can play them (provided I add "dvd://" in front of the path, after I'm done tabbing)
I think the best bet would be to make bash-completion default to normal, unfiltered filename matches if it can't find a specific filetype in its configuration (equivalent to what you'd get without the package installed at all). I think this would solve a number of other problems such as that mentioned in bug #115224 , bug #127605 , bug #156200 , and probably a number of others.
Changed in bash-completion (Ubuntu): | |
status: | New → Confirmed |
You can get default completion behaviour (not the special-case stuff) for a command by doing e.g. \xine. \cmd also disables alias expansion.
The \ just quotes the first letter of the command, but that's enough to disable some stuff that bash would otherwise do.