similar to: tempdir() containing spaces breaks installing source packages

Hi, Installing a source package on Windows using utils::install.packages() with quiet=TRUE fails, while it works with the default quiet = FALSE. The problem seems to be caused by the fact that when quiet = TRUE, stdout and stderr are set to FALSE when calling "R CMD INSTALL" with base::system2() here:

The obvious guess would be that Rstudio is attempting something like redirecting output and getting itself confused. However, it is pretty clearly Their Problem, no? Rstudio has their own support infrastructure. -pd > On 26 Jan 2018, at 09:17 , Andreas Kersting <r-devel at akersting.de> wrote: > > Just noticed that this problem only occurs from within RStudio (v1.1.414). Any

Just noticed that this problem only occurs from within RStudio (v1.1.414). Any ideas why? Am 26.01.2018 um 08:56 schrieb Andreas Kersting: > Hi, > > Installing a source package on Windows using utils::install.packages() > with quiet=TRUE fails, while it works with the default quiet = FALSE. > The problem seems to be caused by the fact that when quiet = TRUE, > stdout and

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",

Full_Name: Vilmos Prokaj Version: 2.5.1 OS: windows Submission from: (NULL) (81.183.3.216) I'm not sure that this is really a bug, if not I do not understand why should it be in this way. Most of the scripts used to build and install new packages calls the R program with the --slave --vanilla command line options. In the INSTALL script however we can find the following lines

I hope it's not too specific in my setup... I've tried with system2 added on the first line, so: Example.R: system2('ls', timeout=5) cat('Start non-interruptable functions\n') sample_a <- sample(1:1e7) sample_b <- sample(1:2e7) matching <- match(sample_a, sample_b) cat('Finished\n') Sys.sleep(10) And in terminal/bash: R --vanilla

According to ?system2, I should be able to direct the output of STDERR to a file by giving the filename as a character vector to the "stderr" argument. But here is what happens. Given a ruby script test.rb (with its executable bit set): #!/usr/bin/env ruby STDOUT.puts "stdout" STDERR.puts "stderr" And the following R code: > t <- tempfile() > res <-

Hi again! While investigating the bug report [*] I found out that on unix, system2 does not quote its `stdin` argument while preparing the command line to launch. It does shQuote the `stdout` and `stderr` arguments, and also the `f <- tmpfile()` variable (which is used if `input` argument is provided), which seems to set a precedent. On Windows, stdin, stdout, and stderr are handled

Hi, The cleanup_pkg() function defined the big tools:::.build_packages() function in tools/R/build.R is currently broken. When Makefiles are used cleanup_pkg() doesn't clean anything because of the way system2() is called. For example, the call to Ssystem() on line 304 (Ssystem is a silent version of system2) is basically trying to do this: >

On Tue, Mar 19, 2019 at 9:59 AM peter dalgaard <pdalgd at gmail.com> wrote: [...] > What you need is something like (NB: single quotes!) > > system2("sh", env = c("VAR='Hello World'"), args = c("-c 'echo $VAR'")) > Hello World Just out of curiosity, do you think it is possible to make this portable, assuming sh is available? On

Hey all, what is wrong with this command: system2("echo", env = c(VAR = "Hello World"), args = c("$VAR")) I am a bit confused, as help("system2") writes about the env option: > character vector of name=value strings to set environment variables. Is this option buggy, or am I using it just wrong? Thanks for your help Henning

Is there any way to capture output (both stdout and stderr) from install.packages? Solutions like sink and capture.output don't work because the install.packages calls out to system2 which is executed in a separate process: test <- capture.output(install.packages("MASS")) The system2 function does have arguments stdout and stderr but afaik these cannot be controlled via

Hi all, I found some strange behaviour, which I think is a bug. Could someone make an account for me on Bugzilla or pass on my report? The problem: When pressing Ctrl-C when a file is sourced in R, run from Terminal (macOS), sometimes the entire session is ended right away, while I just want to stop the script. This is the case when I press Ctrl-C while some functions are running that don?t

I need to run a report, source file on system 1, on system 2. I'd like to do this in one script, not have a second script to run it. Now cat script | ssh system2 works fine. But no matter what I've tried, it gags on ssh system2 <<EOF blah, blah EOF. Mostly, I have a multiline awk script in the script, with \ at the end of each line... *but* I think it's seeing "\n" as

Hi all, I am very new to the rsync world (as well as the linux world) and have some really basic doubts. Please bear with me. I installed RH 9 on two systems in the same network and Rsync 2.5.5 was automatically installed with it. When I executed the command “rsync –avz test.txt /backupdir/ ”, it backed up the file test.txt into backupdir/test.txt. But when I tried the command “rsync

My question: On Windows, R's system() command prepends several directories to those in the Windows Path variable. >From ?system The search path for 'command' may be system-dependent: it will include the R 'bin' directory, the working directory and the Windows system directories before 'PATH'. This shadows any executables on the Path that share a

I have 4 systems and each one of them has a partition I'd like to be remotely accessible on the other 3 systems. In other words System1 has Partition1. Systems 2,3,4 should be able to remotely mount Partition1 from System1. Also System2 has Partition2. Then systems 1,3,4 should be able to remotely mount Partition2 from System2 and so on. I tried NFS and it works but only in the ideal

The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of

Dear R Help, My apologies if this is widely known, but I didn't find this in the R archives. I am running WinXP pro and R 1.90. Rcmd build or check fails with the error: "Please set TMPDIR to a valid temporary directory" $TMPDIR is set to $TMPDIR or C:/TEMP in share\perl\R\Var.pm. TMPDIR or c:\temp do not exist on WinXP on my laptop. I have C:\WUTemp and the env variables

Current R release (3.5.2) and devel return a 0 exit status on error, while prior versions returned a non-zero exit status. On Linux and MacOs, the following line returns TRUE for R-3.5.2 and R-devel, and FALSE for R-3.5.1 and R-3.5.0: system2("Rscript", c("-e", shQuote("stop('foo')"))) == 0 I didn't find this in the NEWS, so I believe this is a bug.