Re: lost output from asynchronous lists

2008-10-29 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 10/29/2008 6:22 AM: >>> - ( :; $1 ) >"$at_stdout" 2>"$at_stderr" >>> + : >"$at_stderr" >>> + ( :; $1 ) >>"$at_stdout" 2>>"$at_stderr" >> What's the ":;" for? > > A workaround to the bash 3.2 bug, fixed in bash32-030, wher

Re: lost output from asynchronous lists

2008-10-29 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Stephane Chazelas on 10/29/2008 3:32 AM: >> Yes. For shell portability, I'll write the first line as >> : > stdout >> : > stderr >> >> though. > > Why? It fails on old Ultrix sh, which can't redirect the same fd more than once in a

Re: lost output from asynchronous lists

2008-10-29 Thread Stephane Chazelas
On Tue, Oct 28, 2008 at 10:51:13PM +0100, Ralf Wildenhues wrote: [...] > > : > stdout > stderr [...] > Yes. For shell portability, I'll write the first line as > : > stdout > : > stderr > > though. Why? I can't see why ": > stdout > stderr" wouldn't work in any shell. It should even work in