On Mon, Feb 12, 2018 at 6:33 PM, Chet Ramey wrote:
>
> Because, as I said in my original reply, readline understands how to
> complete inside quoted strings. If point is after the `b', for instance,
> and you hit TAB, readline scans back to the open quote and passes
> "p/foo/a b" to the completion
On Wed, Feb 7, 2018 at 11:12 PM, Chet Ramey wrote:
>
> You might try, as an intermediate step, removing `'' and `"' from
> $COMP_WORDBREAKS and seeing how that works. I would be interested if it
> affected readline's ability to complete within quoted strings.
>
I have tried this, and it works ok
On Wed, Feb 7, 2018 at 10:56 PM, Chet Ramey wrote:
> On 2/6/18 3:52 PM, Nick Patavalis wrote:
>>
>> In any case, splitting it like:
>>
>> foo | --bar | =" | baz" aa bb
>>
>> (the last part a single word) does not look reasonable to me (even if
&
Hi,
Thank you for your reply.
I'm not sure I understand everything, other than basically... "that's
how readline does it".
I don't suggest there's a bug in readline, but I don't understand, for
example, why
foo --bar "baz" aa bb
is ok to be split like:
foo | --bar | "baz" | aa | bb
while
I witnessed the following in the word-splitting results passed to
custom completion functions. The word splitting performed goes haywire
when it sees the =' (equal, quote) or =" (equal double-quote)
character sequences. From this point on, practically no word-splitting
is performed. As these sequen
