Path: utzoo!attcan!uunet!mcvax!ukc!eagle!icdoc!cam-cl!
From: rbj@arpa.icst-cmr (Root Boy Jim)
Newsgroups: comp.unix.wizards
Subject: Stdio buffering question
Message-ID: <8806151702.AA01534@cmr.icst.nbs.gov>
Date: 15 Jun 88 17:02:17 GMT
Sender: unix-wizards-request@uk.ac.ucl.cs.nss
Lines: 26
To: unix-wizards@mil.brl.sem

? From: Roy Smith <roy@phri.uucp>

? gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
? 
? > I won't accuse [csh] of directing standard error output into pipes.
? > Indeed I think you'd have to work fairly hard to get it to do so.
? 
? 	Depends on what you call "fairly hard"; "foo |& bar" does the trick.

Gee, Doug, RTFM! The 4.2 manual gives the example:
(command > stdout) >& stderr; for some reason it was dropped in the 4.3
manual. The same should work for pipes as well: (cmd1 > stdout) |& cmd2.

Maybe you should *use* something before you put it down.
 
? Roy Smith, System Administrator
? Public Health Research Institute
? 455 First Avenue, New York, NY 10016
? {allegra,philabs,cmcl2,rutgers}!phri!roy -or- phri!roy@uunet.uu.net
 
	(Root Boy) Jim Cottrell	<rbj@icst-cmr.arpa>
	National Bureau of Standards
	Flamer's Hotline: (301) 975-5688
	The opinions expressed are solely my own
	and do not reflect NBS policy or agreement
	My name is in /usr/dict/words. Is yours?