[Top][All Lists]

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

Re: Serious tab completion bug

From: Chet Ramey
Subject: Re: Serious tab completion bug
Date: Sat, 14 Mar 2015 17:30:44 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0

On 3/14/15 10:12 AM, Linda Walsh wrote:
> Chet Ramey wrote:
>> Thanks for the report.  This isn't a bug; it's intentional behavior.  You
>> have presented bash with an ambiguous situation: it doesn't know whether
>> or not you want to look for a filename in the current directory or perform
>> variable expansion.
>> Bash assumes you want filename completion if there's an existing pathname
>> matching the string you typed, so it treats your scenario as filename
>> completion rather than variable expansion.
> ====
>     But that's not what it does.
>     If that was what it did, it would be great, but I agree with the
> original poster.
> if I am in "/tmp", and I try echo $HOME/<complete>, and the pathname
> '$HOME' doesn't exist in /tmp, it will still quote it.

Not by default, so I assume that this is what bash-completion produces.
I corresponded privately with the original poster and he confirmed that
he was using bash-completion.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

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