capture stderr in Windows

An embedded and charset-unspecified text was scrubbed...
Name: not available
Url: https://stat.ethz.ch/pipermail/r-help/attachments/20040816/4c51cb16/attachment.pl
On Mon, 16 Aug 2004 10:25:08 -0700, "Moises Hassan"
<mhassan at scitegic.com> wrote :
I'm using the following command to run R in Windows

"Rterm --no-save --no-restore < "Rscriptfile" > "Rstdoutfile"

How can I capture the text sent by R to stderr in a file?
That depends on your shell.  The standard Windows command shell
COMMAND.COM or CMD.EXE provides no easy way to do this.  There are
lots of replacement shells around that can do it; I use Cygwin's bash
shell most of the time.

There are also programs on the net that do nothing but redirect
standard handles, e.g. <http://www.commandline.co.uk/mtee/index.html>.
I've never tested these.

Duncan Murdoch

I'm using the following command to run R in Windows

"Rterm --no-save --no-restore < "Rscriptfile" > "Rstdoutfile"

How can I capture the text sent by R to stderr in a file?
"Rterm --no-save --no-restore < "Rscriptfile" 2>&1 "Rstdoutfile"

I'd rather use R CMD BATCH anyway.

Uwe Ligges

Thanks, 

   - Moises

	[[alternative HTML version deleted]]

______________________________________________
R-help at stat.math.ethz.ch mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide! http://www.R-project.org/posting-guide.html
I wrote the message below, but it's just plain wrong.

The CMD.EXE shell in Win XP (and 2K?) allows redirection of stderr in
the usual Unix style:

  Rterm --no-save --no-restore < "Rscriptfile" > "Rstdoutfile"
2>"Rstderrfile"

You can also use "2>&1" to redirect stderr into the stdout stream, so
both go to Rstdoutfile.

Duncan Murdoch
On Mon, 16 Aug 2004 10:25:08 -0700, "Moises Hassan" <mhassan at scitegic.com> wrote :

I'm using the following command to run R in Windows

"Rterm --no-save --no-restore < "Rscriptfile" > "Rstdoutfile"

How can I capture the text sent by R to stderr in a file?
That depends on your shell.  The standard Windows command shell COMMAND.COM or CMD.EXE provides no easy way to do this.  There are lots of replacement shells around that can do it; I use Cygwin's bash shell most of the time.

There are also programs on the net that do nothing but redirect standard handles, e.g. <http://www.commandline.co.uk/mtee/index.html>. I've never tested these.

Duncan Murdoch

The CMD.EXE shell in Win XP (and 2K?) allows redirection of stderr in
the usual Unix style:
(Yes, all NT-based versions of Windows.)
  Rterm --no-save --no-restore < "Rscriptfile" > "Rstdoutfile"
2>"Rstderrfile"

You can also use "2>&1" to redirect stderr into the stdout stream, so
both go to Rstdoutfile.
[But the order matters, so first redirect stdout and then redirect stderr 
to stdout.]

And for completeness, 

1) Under non-NT Windows (95/98/ME) stderr is the same as stdout since its 
shells don't know about stderr.

2) This is in all the rw-FAQ, Q2.10
Brian D. Ripley,                  ripley at stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595