krm (11/10/82)
How about a csh facility for redirecting the error port to a file? >& is not what I want since I can't separate errors from output and |& cat > seems like a kludge. Rich.
krm (11/10/82)
How about a csh facility for redirecting the error port to a file? Rich.
krm (11/10/82)
How about a csh facility for redirecting the error port to a file? Like for putting the output into a different file from the errors. Rich.
puder (11/11/82)
Wouldn't it be great if _a_l_l the system programs (including the operating system) passed through lliinntt with nary a complaint? (except for sccsid not referenced, etc.) And I _d_o_n_'_t mean by castrating lliinntt!! (Like redefining it to be ccaatt >> //ddeevv//nnuullll ).
thomas (11/11/82)
Here's another kludge: ( command > stdout-file ) >& stderr-file =Spencer
puder (11/11/82)
References: cwruecmp.257 The Bourne shell (sh) had a great facility for directing any output of a program to a file or to any input of another program. Why doesn't csh do the same?