Chet Ramey dixit:
>> 2. IFS side-effects don't take effect during expansion.
>
>Yeah, this is a tough one. If you want side effects of assignments to IFS
>to affect subsequent expansions, you have to have a way to ensure that the
I think changing IFS during expansion is just asking for trouble.
On 1/30/13 12:16 AM, Dan Douglas wrote:
>>> 3. Another IFS oddity via "command"
>>>
>>> IFS can be given "two values at once" through the environment of a
>>> redirection.
>>
>> I have to look at this one. It's clear that the temporary environment
>> given to `command' is like the temp environm
Hey thanks for all the nice explanations. I'm sure I'll reference this in the
future.
> > 3. Another IFS oddity via "command"
> >
> > IFS can be given "two values at once" through the environment of a
> > redirection.
>
> I have to look at this one. It's clear that the temporary environment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/9/13 2:46 PM, Dan Douglas wrote:
> I'll lump a few issues together here...
>
> 1. Backslash escape adjacent to "$@" expansion separates words.
Yes, this is a bug. I will fix it for the next version.
> $ set -- abc def ghi; printf '<%s> '
I'll lump a few issues together here...
1. Backslash escape adjacent to "$@" expansion separates words.
$ set -- abc def ghi; printf '<%s> ' "123 $@ 456"; echo
<123 abc>
$ set -- abc def ghi; printf '<%s> ' "123 $@\ 456"; echo
<123 abc> <456>
Other shells don't do this (thou
