EspeonEefi wrote:
> This bug is actually breaking completion of all arguments that have
> embedded spaces, whether escaped with \ or within quotes. This bug
> causes completion to be run against just the part of the current word
> after the last space.
I don't see how it is related, I still can't reproduce the test cases
they showed...
> I believe the problem is in _get_cword() (line 185 in
> /etc/bash_completion). More specifically, its method of finding where
> the current word starts is broken. Line 190
>
> word_start=`expr "$cur" : '.*['"${COMP_WORDBREAKS}"']'`
>
> is supposed to find that position, but the regular expression is too
> greedy, and it captures all the way up to the last space, whether that
> space is really the beginning of the word or actually an escaped space
> or a space inside quotes that should be considered part of the word.
Did this work before or is this a feature request? Anyway, I would be
happy to include a patch fixing it.
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
