On 3/28/13 1:05 AM, Dan Douglas wrote:
> On Tuesday, March 26, 2013 08:33:52 PM Chet Ramey wrote:
>
> Thank you. I'm familiar with the declaration commands. It's issue 7, not TC1.
Actually, I don't think it's either. I think we're going to have to wait
until issue 8 for these.
> Are you saying
On Tuesday, March 26, 2013 08:33:52 PM Chet Ramey wrote:
Thank you. I'm familiar with the declaration commands. It's issue 7, not TC1.
> arguments are expanded as normal and then treated as the command
> does its arguments.
Are you saying here that even when a declaration command is _not_ identi
On 3/25/13 9:44 PM, Dan Douglas wrote:
> Hi,
>
> $ set -x; foo=bar declare arr=( {1..10} )
> + foo=bar
> + declare 'a=(1)' 'a=(2)' 'a=(3)' 'a=(4)' 'a=(5)'
>
> $ touch xy=foo
> $ declare x[y]=*
> + declare 'x[y]=*'
> $ foo=bar declare x[y]=*
> + foo=bar
> + dec
Hi,
$ set -x; foo=bar declare arr=( {1..10} )
+ foo=bar
+ declare 'a=(1)' 'a=(2)' 'a=(3)' 'a=(4)' 'a=(5)'
$ touch xy=foo
$ declare x[y]=*
+ declare 'x[y]=*'
$ foo=bar declare x[y]=*
+ foo=bar
+ declare xy=foo
This isn't the same bug as the earlier a=([n]=*) i
