That's sad. Thank you anyway.
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
[EMAIL PROTECTED] wrote:
>> > XXX=10; { XXX=20; } | read; echo $XXX
>
> It's clear that 'read' is executed as an separate process and its
> result (REPLY variable value) is lost but 'XXX=20' command is done by
> the same process as 'XXX=10'.
No, every element of a pipeline is executed in its own
> XXX=10; { XXX=20; } | read; echo $XXX
>
> XXX=10; { XXX=20; }; echo $XXX
>
> I suppose both of them should output '20' but the first one outputs
> '10'. Is it feature of bug?
This is normal. It's explained in entry E4 in the bash FAQ.
Oh, sorry, I made a mistake in the subject, it should ha
[EMAIL PROTECTED] wrote:
> XXX=10; { XXX=20; } | read; echo $XXX
>
> XXX=10; { XXX=20; }; echo $XXX
>
> I suppose both of them should output '20' but the first one outputs
> '10'. Is it feature of bug?
This is normal. It's explained in entry E4 in the bash FAQ.
paul
_
Hi, bash developers!
I've noticed strange bash behaviour. If I assign variable value in
right behalf of pipeline it has no effect. Just try to execute:
XXX=10; { XXX=20; } | read; echo $XXX
XXX=10; { XXX=20; }; echo $XXX
I suppose both of them should output '20' but the first one outputs
'10'
