Re: Completion of ENV variables seems to be broken - leading slash (or even more) is added

[Chet Ramey]

On 12/9/21 3:41 AM, Guillaume Outters wrote:

> The idea behind: the part that the user typed is considered well formed 
> (sufficently to return matches),
> so try to preserve it, and do quote only the completion's additions.

I used an idea that already existed in the bash completion code (I made it
bash-specific since the issue of word expansion is specific to bash, not
general to applications using readline). It assumes that any unquoted
word expansion characters are intended to eventually be expanded, and
quotes accordingly.

There was enough existing code there to do it without adding much new.

Chet

--
``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/