Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14346 > unrolled thread

Re: ${parameter@A} doesn't work should no value be set

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: ${parameter@A} doesn't work should no value be set Chet Ramey <chet.ramey@case.edu> - 2018-07-15 18:19 -0400

#14346 — Re: ${parameter@A} doesn't work should no value be set

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/

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web