-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 7/9/2009 6:13 AM:
> In looking at it further, one of the differences is that zsh enables
> notify mode (set -b) by default, although POSIX states that notify mode
> should default to off (set +b). 'emulate sh' does not chang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 7/10/2009 6:14 AM:
> Does this help?
> * doc/autoconf.texi (Preset Output Variables): Add a paragraph.
> * THANKS: UPdate.
> Reported by Monty Taylor.
Committed.
- --
Don't work too hard, make some time for fun as well!
E
On 07/13/2009 01:26 PM, Eric Blake wrote:
{ echo "set -$-"; COMMAND; } | sh
This does it, yes.
(You've been using too many fifos for the parallel autotest :-).
Paolo
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Alfred M. Szmidt on 7/13/2009 5:06 AM:
> { set +o; COMMAND; } | sh
Required by POSIX, but some older shells don't handle it well. Solaris
/bin/sh appears to just ignore it. Older ash gives output that cannot be
reparsed as valid c
Hi autoguys,
I am piping the output of a script to the shell, and using
COMMAND | sh
would not respect the -e/-x settings of the outer shell. I have thought
of two replacements:
{ set +o; COMMAND; } | sh
COMMAND | . /dev/fd/0
The second looks nicer, but it's
Hi autoguys,
I am piping the output of a script to the shell, and using
COMMAND | sh
would not respect the -e/-x settings of the outer shell. I have thought
of two replacements:
{ set +o; COMMAND; } | sh
COMMAND | . /dev/fd/0
The second looks nicer, but it's not portable. Actually I
