Farrell Woods writes:
> Near as I can tell, csh and its derivatives (tcsh for instance) don't
> provide for sending stderr to a separate file if stdout is also being
> redirected. I'm at a loss to explain this as it seems like quite a
> regression in basic functionality. (Though I'm sure if I'm wrong or
> if there's a stunt that allows separation of the streams then someone
> will write a note within a few milliseconds of reading this one... :-) )
Oh, sure, in csh here's how you'd redirect stderr to someplace other
than where stdout is going:
sh -c 'find . -name foo -print >someFile 2>errorFile'
I.E. if you want this functionality, you'd better use the Bourne
shell, because csh is famous for not offering this functionality.
I don't know about everybody else, but I need this functionality all
of the time, including in interactive shells. Therefore the csh is
useless to me.
--kevin
--
The C-shell doesn't parse. It adhoculates.
- [EMAIL PROTECTED] in <3ol96k$[EMAIL PROTECTED]>
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
