bug-bash
[Top][All Lists]
Advanced

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

Re: Autocompletion problems with nounset and arrays


From: Chet Ramey
Subject: Re: Autocompletion problems with nounset and arrays
Date: Thu, 19 May 2016 15:07:06 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0

On 5/19/16 2:54 PM, Siteshwar Vashisht wrote:
> 
> 
> ----- Original Message -----
>> From: "Chet Ramey" <address@hidden>
>> To: "Eric Pruitt" <address@hidden>, address@hidden, address@hidden
>> Cc: "chet ramey" <address@hidden>
>> Sent: Tuesday, April 26, 2016 11:24:12 PM
>> Subject: Re: Autocompletion problems with nounset and arrays
>>
>> Thanks for the report.  I will fix this before bash-4.4 is released.
> 
> I have built bash from devel branch and I am still able to reproduce this 
> bug. Also, this bug is reproducible if I try to complete path names instead 
> of arrays.

Sorry, I am afraid you misunderstood my response.  The original report
concerned bash's built-in word completion, and the change you refer to
fixes that case.  It's not visible to users, since it changes the
setting temporarily in a place where users cannot do it.

You're using the bash_completion package, and it does not handle running
with `-u' enabled very well.  I don't think bash should be changing
something where it ends up being user-visible to compensate for a case
the script didn't anticipate -- that's the script's business.

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