[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ${parameter@A} doesn't work should no value be set
|
From: |
Chet Ramey |
|
Subject: |
Re: ${parameter@A} doesn't work should no value be set |
|
Date: |
Sun, 15 Jul 2018 18:19:27 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
On 7/14/18 3:10 PM, Michal Pesa wrote:
> Bash Version: 4.4
> Patch Level: 19
> Release Status: release
>
> Description:
> Hello, I would like to report a bug or rather a feature I think should be
> implemented. The new parameter expansions ${parameter@A} and ${parameter@a}
> don't work if only attributes are set but value is not.
The ${parameter[op[word]]} expansion generally (except where explicitly
noted) expand to nothing when `parameter' is unset. I can see making an
exception for ${parameter@a}, though, since it displays only the
attributes. I'll take a look at that.
--
``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/