[Bash-completion-devel] Bug with key=value options?
Ville Skyttä
ville.skytta at iki.fi
Sun Jan 8 20:28:36 UTC 2012
On 2012-01-08 18:15, David Paleino wrote:
> I'm attaching the "set -x" output when I do foo bar=b<TAB> (truly speaking,
> it's bar=ac<TAB>, trying to complete some aclocal.m4 I have in the current
> directory).
>
> Would you mind comparing it to yours?
Mine is attached.
Differences start in the beginning of __reassemble_comp_words_by_ref
(the - one being yours, the + one mine):
-+ exclude='<>&'
++ exclude='=<>&'
For some reason, your version doesn't end up excluding the equals sign
from COMP_WORDBREAKS; dunno why but I can see how things can go south
from there.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: set-x-ville.log
Type: text/x-log
Size: 5375 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/bash-completion-devel/attachments/20120108/37999175/attachment-0001.bin>
More information about the Bash-completion-devel
mailing list