From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11040 invoked from network); 24 Mar 2002 16:47:58 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 24 Mar 2002 16:47:58 -0000 Received: (qmail 6431 invoked by alias); 24 Mar 2002 16:47:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16891 Received: (qmail 6420 invoked from network); 24 Mar 2002 16:47:50 -0000 From: Borsenkow Andrej To: Zsh hackers list Subject: Re: Piping stderr (was Re: Two bug reports) In-Reply-To: References: Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution/1.0.2-4mdk Date: 24 Mar 2002 19:47:27 +0300 Message-Id: <1016988453.3443.1.camel@localhost.localdomain> Mime-Version: 1.0 =F7 =F7=D3=CB, 24.03.2002, =D7 12:01, Wayne Davison = =CE=C1=D0=C9=D3=C1=CC: >=20 > > The problem being that in order to pipe "just stderr" you have > > to dispose of stdout somehow. >=20 > No, stdout doesn't need to be affected at all. If the user wants = stdout > to go somewhere other than the default, it can be redirected = explicitly > (as I did above). >=20 That makes sense. More than once I wished to pipe stderr while leaving stdout alone. -andrej