Bleh I'm wrong, brace expansion remains too. I should know this... it's hard to
remember all the quirks even when I write them down.
On Saturday, August 18, 2012 07:55:17 PM Stephane Chazelas wrote:
> 2012-08-18 10:26:22 -0500, Dan Douglas:
> > This is a feature that all shells with this style of compound assignment
> > have
> > in common. If no explicit subscripts are given, the text between the
> > parentheses is processed
2012-08-18 10:26:22 -0500, Dan Douglas:
> This is a feature that all shells with this style of compound assignment have
> in common. If no explicit subscripts are given, the text between the
> parentheses is processed exactly as though it were arguments to a command
> including brace expansion,
This is a feature that all shells with this style of compound assignment have
in common. If no explicit subscripts are given, the text between the
parentheses is processed exactly as though it were arguments to a command
including brace expansion, word-splitting, and pathname expansion (and
con
This is a question about bash's behaviour concerning assignment to array
members.
Bash Version 4.2.24(1)-release (x86_64-pc-linux-gnu)
The bash manual (version 4.1, chapter 3.4) says about assignment
to shell variables: "Filename expansion is not performed."
simple test to proof this on the co
On Fri, Aug 17, 2012 at 10:19 AM, John Summerfield wrote:
(...)
> The man page for bash contains a para entitled ENVIRONMENT which doesn't
> mention arrays, leaving the reader to assume they are not different from
> other shell variables.
the BUGS section contains:
Array variables may not (yet) b
