similar to: [PATCH] file.access returns success for NA

Below is a patch for setwd() to show path in error message. Current it just gives error messages such as: Error in setwd(libdir) : cannot change working directory with the patch it should (read untested) give: Error in setwd(libdir) : cannot change working directory to 'path/that/fails/' PATCH: % diff -u util.c "util,patch.c" --- util.c 2012-12-16 13:13:05.002249900

tools::md5sum gives a warning if it receives a directory as an argument on Unix but not on Windows. >From what I understand, this happens because in Windows a directory is not treated as a file so fopen returns NULL. Then, NA is returned without a warning. On Unix, a directory is treated as a file so fopen does not return NULL so md5 is run and fails, leading to a warning. This is a good

Rscript eats up the last argument when reporting the command it runs: $ Rscript --verbose "/tmp/test.R" one two three running '/usr/local/lib/R-devel/lib/R/bin/R --slave --no-restore --file=/tmp/test.R --args one two' With the patch below, I get the following: $ Rscript --verbose "/tmp/test.R" one two three running '/usr/local/lib/R-devel/lib/R/bin/R --slave

I have two comments regarding the Posting Guide: (1) The link in the following sentence did not work for me: Take care when you quote other people's comments to respect their rights, e.g., as summarized here[a]. [a] http://www.jiscmail.ac.uk/help/policy/copyright.htm Has it been changed to the following? http://www.jiscmail.ac.uk/policyandsecurity/copyrightissues.html (2) Regarding

Below is an example of output that changed as a result of r64970. I did not see any NEWS item suggesting this change is expected. Note that the example is contrived and I don't have a use case for it. I stumbled across it when playing with recent changes in R relating to duplication. Does the example use undefined syntax? ----- fn1 <- function(mylist) { fn1a <- function()

Hi, I am using a local patch to have CMD check exit with error if there is a note or warning. Am I missing an already existing way to do this? If not, Is there any interest in having an option or environment variable for this upstream? I would be interested in making a patch. If so, option or environment variable? Any suggestions for the name? Should this be two options or one option with

I don't know if this is a bug. I can reproduce the following on Ubuntu 12.04.2 and 13.04 64-bit with R version 3.0.1 and with r63479. There is no difference if R is patched with the fix for PR#15407 or not, although without the fix there are more ways to trigger this. I can reproduce with the following: 1. Open R in gnome-terminal or xterm 2. Run 'library(tcltk)' 3. Run

Dear list, ?require says : "... |require| is designed for use inside other functions; it returns |FALSE| and gives a warning (rather than an error as |library()| does by default) if the package does not exist ..." However when I run the following code I don't get any TRUE / FALSE statements (but the warning only). Since I want to test from inside of a function if a given package

The following example in ?dump.frames options(error = quote({dump.frames(to.file = TRUE); q()})) is useful for teaching the user how to save a frame dump when R encounters an error during non-interactive sessions. This command however causes an additional change that on encountering an error R exits with a 0 error status. Although it's just an example, it's an important one as it's

The command "ssh ls -l /doesnotexist" gives various responses: Running from a 200 MHz PentiumPro with dsa key added to ssh-agent: Mistakes worst to fast machine: To a faster 600 MHz dual processor i686 600 MHz machine: ls: /doesnotexist: No such file or directory -- correct nothing at all -- wrong ls: select: Bad file descriptor -- wrong

Regarding the following extract of ?options: ?editor?: a non-empty string, or a function that is called with a file path as argument. edit.default currently calls the function with three arguments: name, file, and title. For example, running the following vimCmd <- 'vim -c "set ft=r"' vimEdit <- function(file_) system(paste(vimCmd, file_)) options(editor =

Attached is a patch with minor suggestions for the R-ints manual at r64048. The most substantial change is the following: The top layer comprises the graphics subsystems. Although there is -provision for 24 subsystems, after 6 years only two exist, `base' and +provision for 24 subsystems, since 2001 only two exist, `base' and `grid'. Is the year 2001 correct? I base it on the date

Dear R-help, Call RInterface.StartRServer ' Works fine Call RInterface.RRun("objects()") ' Works fine Call Rinterface.RRun( other R commands which do not generate errors, the demos etc ) ' Works fine But ... Call RInterface.RRun("doesnotexist") ' Sends Excel into endless loop it appears After about 90 seconds a dialog box appears "Microsoft

I see another thing in function 'NewName' in bind.c. In else if (*CHAR(tag)) , 'ans' is basically copied from 'tag'. Could the whole thing there be just the following? ans = tag; It seems to me that it can also replace ans = R_BlankString; in 'else'; so, else if (*CHAR(tag)) and else can be merged to be just else . --------------------------------------------

For the 2nd example, I say that R 3.4.1 result is acceptable, as names(c(x)) and names(x) are equal. The change exposed by the 2nd example is in line with statement of the NEWS item corresponding to PR#17284: "c() and unlist() are now more efficient in constructing the names(.) of their return value, ...." However, currently, the NEWS item is for R-devel, not R 3.4.1 patched.

On 04/01/2020 4:35 p.m., Scott Kostyshak wrote: > On Fri, May 31, 2019 at 01:28:55AM -0400, Scott Kostyshak wrote: >> The attached patch adds some sanity checks to the "type" argument of ... > Bump. For this type of patch proposal, is it better to use the > bug tracker? For almost any patch proposal it is. Certainly if you don't get action (or at least discussion)

On Fri, May 31, 2019 at 01:28:55AM -0400, Scott Kostyshak wrote: > The attached patch adds some sanity checks to the "type" argument of > quantile(). Output from the following commands show the change of > behavior with the current patch: > > vec <- 1:10 > quantile(vec, type = c(1, 2)) > quantile(vec, type = 10) > quantile(vec, type = "aaa")

Attached is a patch with suggestions for the R-lang manual at r64277. Below are a few comments (some are implemented in the patch): In the section "Objects", there is a table introduced by "The following table describes the possible values returned by typeof". One of the results is "any". Can "any" be returned by "typeof()" ? Regarding the

The other day I was working on an example which used tempfile() to create file for use by the graphics device. And while I love tempfile()---as it is portable and clever and the files get cleaned by R and all that---I noticed one missing feature I would like to see: beside a starting name pattern, and an optional directory, an 'file extension' argument would be nice to have. As e.g. in

Since R 2.5.0 it has been possible to declare the encodings of character strings (at the level of individual elements of a character vector). As a reminder, here is the announcement in NEWS o R now attempts to keep track of character strings which are known to be in Latin-1 or UTF-8 and print or plot them appropriately in other locales. This is primarily intended to make it possible