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 c...@case.edu http://cnswww.cns.cwru.edu/~chet/
