similar to: Bug in RScript.exe for 3.5.0

Fixed in R-devel. I will port to R-patched after more testing. Tomas On 04/26/2018 01:52 AM, Tomas Kalibera wrote: > Thanks for the report. A quick workaround before this gets fixed is to > add an extra first argument that has no space in it, e.g. > > Rscript --vanilla "foo bar.R" > > The problem exists on all systems, not just Windows. > > Best > Tomas >

Hi Tomas, Thanks for the info about the binary builds; I did install it, however the bug still seems to be there in the current build. The workaround you suggested does work: C:\>"C:\Program Files\R\R-devel\bin\x64\Rscript.exe" "C:\foo bar.R" Fatal error: cannot open file 'C:\foo': No such file or directory C:\>"C:\Program

Thanks Tomas. I confirm the quick workaround works for me in the DOS prompt, and when having a shortcut to RScript in SendTo, and when used in the Task Scheduler. I have not tested the R-devel version, due to my unfamiliarity with installing from source code. -----Original Message----- From: Tomas Kalibera [mailto:tomas.kalibera at gmail.com] Sent: Thursday, April 26, 2018 6:34 AM To: Kerry

Thanks Tomas, I confirm the R Under development (unstable) (2018-04-26 r74651) version works for Rscript when the file name has a space, and no arguments are specified. C:\>"C:\Program Files\R\R-devel\bin\x64\Rscript.exe" "C:\foo bar.R" R Under development (unstable) (2018-04-26 r74651) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows 7 x64 (build 7601)

On 04/26/2018 02:23 PM, Kerry Jackson wrote: > Thanks Tomas. > > I confirm the quick workaround works for me in the DOS prompt, and when having a shortcut to RScript in SendTo, and when used in the Task Scheduler. I have not tested the R-devel version, due to my unfamiliarity with installing from source code. Thanks, Kerry. There are binary builds for daily snapshots of R-devel

Thanks, actually this is because the snapshot build is still one version behind (74642, the fix is in 74643). When I build my own installer and install it seems to be working fine. Sorry for the confusion, Tomas On 04/26/2018 02:49 PM, Kerry Jackson wrote: > Hi Tomas, > > Thanks for the info about the binary builds; I did install it, however the bug still seems to be there in the

It seems the fix has not been ported to the patched version of R on Windows yet. I just tested R version 3.5.0 Patched (2018-04-27 r74667). IMHO this bug is so bad that it is worth a new release R 3.5.1 before it starts biting more users like this one https://stackoverflow.com/q/50077412/559676. BTW, although the bug has been fixed (https://github.com/wch/r-source/commit/c29f694), I think it will

Thanks for the report. A quick workaround before this gets fixed is to add an extra first argument that has no space in it, e.g. Rscript --vanilla "foo bar.R" The problem exists on all systems, not just Windows. Best Tomas On 04/25/2018 09:55 PM, Kerry Jackson wrote: > Hi R Developers, > I have found what I think is a bug in the RScript.exe in version 3.5.0 of R for Windows.

> Dear Tomas, > > thank you for fixing the bug, I still do not find it mentioned in the > changelog though (neither R-patched nor R-devel), also, see inline below > > On Sat, Apr 28, 2018 at 11:36 PM, Tomas Kalibera <tomas.kalibera at gmail.com > > wrote: > >> >> I don't have an opinion if this requires 3.5.1 to be released soon(er), >> but I

See the example below (under Ubuntu): $ Rscript -e '1' -e '2' [1] 1 [1] 2 $ Rscript -e '1' -e '' -e '2' ERROR: option '-e' requires an argument $ uname -a Linux xie 3.5.0-25-generic #39-Ubuntu SMP Mon Feb 25 18:26:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Similar problem under Windows: Rscript -e "1" -e "" -e "2" [1]

Hi, I'm trying to run on Windows 7 a scriptfile with Rscript.exe from within Excel 2010 with the following code: Call Shell(rPath & "\Rscript.exe C:\Work\Latest\_Test.R", vbHide) The good news is: the above code works perfectly, but ... If I add white spaces to my map directory, like: Call Shell(rPath & "\Rscript.exe C:\Work\Latest 1\_Test.R", vbHide) In the

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.

>>>>> Martin Maechler >>>>> on Mon, 28 May 2018 10:28:01 +0200 writes: >>>>> Ralf Stubner >>>>> on Fri, 25 May 2018 19:18:58 +0200 writes: >> Dear all, I would like to draw you attention to this >> question on SO: >>

Hi, A user of my `optparse` package discovered a bug in Rscript's parsing of [args]. (https://github.com/trevorld/optparse/issues/24) I've reproduced the bug on my machine including compiling and checking the development version of R. I couldn't find a mention of it in the Bug Tracker or New Features. Can be minimally reproduced on the UNIX command line with following commands:

Greetings, I am creating a standalone executable script using Rscript and have run into problems when I define a new S4 class. Here is a small script that demonstrates my problem: #!/usr/bin/env Rscript # # toy.Rscript -- testing S4 class creation in an Rscript setClass("toy", representation(name = "character", price = "numeric"),

Dear all, finally decided to do an Ubuntu upgrade and a new clean R install from http://cran.r-project.org/bin/linux/ubuntu/. However, while trying to install a package from R-forge I encountered problems, involving error messages saying "Rscript execution error: No such file or directory" (see below). The same procedure works on Ubuntu 11.04 running R 2.12.1-1 from the Ubuntu

Good morning R-help, I have an idiot question: I would like to use getSrcDirectory() and friends to allow me to identify where an R file has been called from when invoked using Rscript. If I understand the documentation correctly, the following example should work: In file test.R: options(keep.source=T) fn<-function(x){x<-x+1} srcDir<-getSrcDirectory(fn) print(srcDir) I

One of the examples in Rscript.Rd seems mis-formatted, in that the format statement is incomplete: ## Not run: Rscript -e 'date()' -e 'format(Sys.time(), " Both Rscript.Rd in R 2.5.0 and the version at: https://svn.r-project.org/R/trunk/src/library/utils/man/Rscript.Rd have Rscript -e 'date()' -e 'format(Sys.time(), "%a %b %d %X %Y")' Do

Hi all, this is probably some tricky configuration file problem, but I figure someone here might have come across this in the past: In short, I've been using Rscript to run my scripts, usually successfully. But recently I've run into a strange problem, and the only function that causes an error is "print". I can create a file that contains only a print command, and it causes

Hi: I have also just stumbled into this bug. Unfortunately, I can not change the data my program receives from stdin. My code runs in a larger system and stdin is sent to a Docker container running my R code. The protocol is I read a line, readLines("stdin", n=1), do some actions, send output on stdout, and wait for the next set of data. I don't have control over this protocol, so