On Wed, 10 Mar 1999, Jeremy Wadsack wrote:
>
> Hmm... Maybe we've different definitions of 'analog output'. What I want in for
> analog to create the report file as it normally does (which is what the OUTFILE
> command is for), but when I run it it sends all warnings and errors to the
> screen. These are what I'm trying to capture to a log file for later perusal. I
> would expect to beable to run a command like
> analog > analog.log
> And have analog read and interpret analog.cfg, read logs specified in LOGFILE,
> write a report to the file specified in OUTFILE and have any warning messages
> and error appear in analog.log.
>
> I hope that is clearer. Is there a way to do this?
>
Oh, I see. Well, errors go to standard error. Does anyone know how to redirect
stderr in Windows?
Or else, should the user be able to specify a file for this instead? In some
ways that's an attractive idea, but in other ways I'm worried that people will
set the ERRFILE, forget they've set it, and then not see any error/warnings
messages. I suppose -- I'm thinking as I type here -- setting the ERRFILE
could generate a message to stdout as a side effect.
--
Stephen Turner [EMAIL PROTECTED] http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"Ad infinitum, if not ad nauseam." (Interviewee, BBC Radio 4)
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
