Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: losing stderr messages

X-seq: zsh-users 10380
From: Frank Terbeck <frank.terbeck@xxxxxxxxxxxxxx>
To: zsh list <zsh-users@xxxxxxxxxx>
Subject: Re: losing stderr messages
Date: Fri, 16 Jun 2006 11:36:28 +0200
In-reply-to: <200606160921.k5G9Lh9F004976@xxxxxxxxxxxxxx>
Mail-followup-to: zsh list <zsh-users@xxxxxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
Operating-system: Linux 2.6.16.16 i686
References: <20060616085843.GA27632@xxxxxxxxx> <200606160921.k5G9Lh9F004976@xxxxxxxxxxxxxx>

Peter Stephenson <pws@xxxxxxx>:
> Charles Hallenbeck wrote:
> > I have a command sequence which works as expected when bash is the
> > default shell (/bin/sh) but which fails to capture stderr output when
> > /bin/sh points to zsh. Can someone tell me why, and better yet how to
> > find the missing stderr messages? The sequence is:
> > 
> > { ./configure && make && make install } &> log &
> 
> This should work fine.  Most people would probably write ">&" but they
> have the same effect.  The problem may be deeper inside the scripts.

Oops, I always thought '&>' didn't work in zsh, but I was wrong.
So, the OP can ignore my Statement about that.

Regards, Frank

References:
- losing stderr messages
  - From: Charles Hallenbeck
- Re: losing stderr messages
  - From: Peter Stephenson

Messages sorted by: Reverse Date, Date, Thread, Author