Xref: utzoo comp.sources.wanted:9451 alt.sources.wanted:34
Path: utzoo!hoptoad!unisoft!greywolf
From: greywolf@unisoft.UUCP (The Grey Wolf)
Newsgroups: comp.sources.wanted,alt.sources.wanted
Subject: Re: separate redirection of stderr and stdout in csh.
Message-ID: <2621@unisoft.UUCP>
Date: 18 Nov 89 05:01:44 GMT
References: <13928@teraida.UUCP> <8607@cbmvax.UUCP>
Reply-To: greywolf@unisoft.UUCP (The Grey Wolf)
Organization: none whatsoever.
Lines: 27

In article <8607@cbmvax.UUCP> kevin@cbmvax.UUCP (Kevin Klop) writes:
>In article <13928@teraida.UUCP> jeffy@teraida.UUCP (Jeffrey Youngstrom) writes:
>>Hiya,
>>	In the bourne shell I can do this:
>>
>>		#!/bin/sh
>>
>>		dumb_command 1> good_stuff 2> errors
>>
>>	to send the output of my command to good_stuff, and
>>	any error messages to a file called errors.
>
>well, dumb_command >&somestuff [ works for csh...almost -- greywolf ]
>
>will redirect stderr out to somestuff.  It has the unfortunate side effect
>of ALSO redirecting stdout as well.  I don't believe that there's a way
>to affect this.
>
>                              -- Kevin Klop --

Try this:

	( dumb_command > good_stuff) >& errors
-- 
"Insane I may be.  I am not stupid."	Antryg Windrose <the mad wizard>
-- 
"Insane I may be.  I am not stupid."	Antryg Windrose <the mad wizard>