bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Space vs. non-space separators in COMP_WORDBREAKS


From: Chet Ramey
Subject: Re: Space vs. non-space separators in COMP_WORDBREAKS
Date: Mon, 20 Dec 2021 09:21:54 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.0

On 12/17/21 9:20 PM, konsolebox wrote:

But that doesn't explain why the spaces are removed and I can't find
anywhere in the documentation of readline that explains it.  I would
have to study the code itself to know why.

Because nobody wants empty arguments to deal with, but it's useful to
know where readline splits the words when it finds the word it wants to
be completed.


Ok but anyway, shouldn't this be mentioned in the manual?  It's pretty
much intuitive that if space is removed (which is the first one easily
noticed), so should other separators specified in COMP_WORDBREAKS.

Except that turns out not to be useful. It's intuitive to say that
whitespace separates words and the non-whitespace word break characters
allow you to complete on parts of words.

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]