According to the manual, the `stdout` argument of the `system2` function can redirect output to a file. This seems to work on unix, however I can't get it to work on windows. The toy example below, no `out.txt` or `err.txt` files are created. I tried sending it to an existing file, or expand the full file path, but with no success: setwd(tempdir()) system2("whoami", stdout="out.txt", stderr="err.txt") file.exists("out.txt") Am I doing something wrong or is this not supported on windows?
Gabor Grothendieck
2013-Jul-14 20:24 UTC
[Rd] Redirect system2 stdout to a file on windows
On Sun, Jul 14, 2013 at 1:18 PM, Jeroen Ooms <jeroen.ooms at stat.ucla.edu> wrote:> According to the manual, the `stdout` argument of the `system2` > function can redirect output to a file. This seems to work on unix, > however I can't get it to work on windows. The toy example below, no > `out.txt` or `err.txt` files are created. I tried sending it to an > existing file, or expand the full file path, but with no success: > > setwd(tempdir()) > system2("whoami", stdout="out.txt", stderr="err.txt") > file.exists("out.txt") > > Am I doing something wrong or is this not supported on windows? > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-develTry: out.txt <- normalizePath("./out.txt", mustWork = FALSE) -- Statistics & Software Consulting GKX Group, GKX Associates Inc. tel: 1-877-GKX-GROUP email: ggrothendieck at gmail.com
Possibly Parallel Threads
- system2 doesn't quote stdin on unix, unlike stdout, stderr & input and on Windows
- Capture output of install.packages (pipe system2)
- Inconsistant result for normalizePath on Windows
- normalizePath is sometimes very slow for nonexistent UNC paths
- utils::install.packages with quiet=TRUE fails for source packages on Windows