The root cause is how bash itself handles curlies:
$ bash --norc
$ foo() { echo; echo '$1'; }
$ complete -D -F foo
$ r drivers/memory/tegra/tegra{-,124-e}mc.c driTAB
'-,124-e}mc.c'
...i.e. bash thinks we're completing the command '-,124-e}mc.c'.
I don't think we can sanely fix this for real in
On Sun, Nov 2, 2014 at 7:23 PM, Raphaël raphael.d...@gmail.com wrote:
Attached a quick patch.
The patch does not apply against current git. Also, this stuff should
be documented somewhere, README or doc/bash_completion.txt
As personal completions could probably be stored in a versioned
losetup completion is shipped by util-linux, not bash-completion.
I just sent a patch upstream that should address this particular issue:
http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/10186
However other completions in util-linux may invoke commands (other
than the one being
