From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5102 invoked from network); 16 Jul 1999 04:12:08 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 16 Jul 1999 04:12:08 -0000 Received: (qmail 28919 invoked by alias); 16 Jul 1999 04:11:53 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2443 Received: (qmail 28912 invoked from network); 16 Jul 1999 04:11:51 -0000 To: zsh-users@sunsite.auc.dk Path: mason From: mason@primenet.com.au (Geoff Wing) X-Newsgroups: lists.zsh.users Subject: Re: pipe on stderr Date: 16 Jul 1999 04:11:43 GMT Organization: PrimeNet Computer Consultants Distribution: local Message-ID: References: "Didier Verna"'s message of "15 Jul 1999 18:23:29 DFT." <9907151608.AA29292@ibmth.df.unipi.it> Reply-To: mason@primenet.com.au NNTP-Posting-Host: coral.primenet.com.au X-Trace: coral.primenet.com.au 932098303 5093 203.43.15.2 (16 Jul 1999 04:11:43 GMT) X-Complaints-To: usenet@coral.primenet.com.au NNTP-Posting-Date: 16 Jul 1999 04:11:43 GMT User-Agent: slrn/0.9.5.6 (UNIX) Peter Stephenson typed: :Didier Verna wrote: :> I've only recently discovered that there's no simple way, in any :> shell, to pipe stderr on another process. As you can write `foo 2> foo.err', :> wouldn't it be nice to be able to write `foo 2| bar' ? Simple way? Sort of. % foo 2>>(bar) # same as foo 2> >(bar) Regards, -- Geoff Wing : Work URL: http://www.primenet.com.au/ Rxvt Stuff : Ego URL : http://pobox.com/~gcw/ Zsh Stuff : Phone : (Australia) 0413 431 874