On 2/7/18 5:09 PM, Nick Patavalis wrote:
> 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
>>
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 2/7/18 5:11 PM, Nick Patavalis wrote:
> On the other hand, readline seems not to be able to complete something
> like:
>
> ls /tm"p/foo/a b"
>
> (and I don't understand why), though this is true, regardless of
> whether " is in COMP_WORDBREAKS or not. I *both* cases, the command line
> is
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
>> it may be convenient in some occasions I cannot t
On 2/6/18 3:52 PM, Nick Patavalis wrote:
> Hi,
>
> Thank you for your reply.
>
> I'm not sure I understand everything, other than basically... "that's
> how readline does it".
You might try, as an intermediate step, removing `'' and `"' from
$COMP_WORDBREAKS and seeing how that works. I would be
On 2/6/18 3:52 PM, Nick Patavalis wrote:
> 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
>
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
On 2/5/18 2:25 AM, Nick Patavalis wrote:
> 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, practicall
