similar to: file.exists does not like path names ending in /

I'm writing to ask if R Core would make file.exists more Windows tolerant when the argument has a trailing slash. This has been discussed by users a few times here, I know it is not a new topic. But it is not a solved problem, yet. I acknowledge that CRAN packages exist which fix this by replacing file.exists(), but it seems more elegant to me to fix the problem in R itself. R Core goes to

Hi all, I saw a quite surprising result in the devel R when using the function *normalizePath*. If the input is a path to a folder, the function returns an absolute path with/without a slash at the end depending on the existence of the folder. I know both results are valid on Windows but this behavior is different than R3.6, I do not know if the change in the devel version is made on purpose.

Hi, Back in June I posted the message below, but had no replies. I've made a little progress since then so this is to update anyone interested (!) and to ask for comments. Brief problem statement: Under Windows, some parts of R don't handle UNC paths beginning with backslashes. Specifically a) Sys.glob() fails to find some files breaking (e.g.) Rcmdr plugins

This request stems off a bug report I posted https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17757 where it was determined the current behaviour is as expected. To recap: when given a real file, normalizePath() always* returns the full absolute path. When given a non-existent file, normalizePath() returns a full path on Windows but it returns the input on other systems*. I'd argue that

I'm having an issue with occasionally slow-running calls to normalizePath. If the path is a non-existent UNC path, then normalizePath sometimes takes 6 or 7 seconds to run, rather than its usual few microseconds. My big problem is that I can't reliably reproduce this across machines. The example below generates one or two slow runs out of 10000 on my Windows machine. I haven't been

> On Nov 23, 2017, at 4:34 AM, Loris Bennett <loris.bennett at fu-berlin.de> wrote: > > Hi, > > TL;DR > ----- > > I define the path > > /cm/shared/apps/R/site-library/3.4.2 > > and add it to libPath. Why does libPath then display it as > > /cm/shared/apps/R/site-library/3.4 > > ? > Because it is a symbolic link.

Does R have a standard function that takes two file paths (e.g., "./myDirectory/file" and "myDirectory/file") and returns TRUE if those paths refer to the same file? The paths make take different routes ("absolute" or relative paths or via different symbolic or hard links) to the same file or may use different naming conventions (Windows or DOS 8.3 on Windows). If

Dear all, I'm not sure whether this is intended behaviour or a bug. The path returns from normalizePath is different when the directory doesn't exist. I have included a reproducible example. path <- tempfile() missing.dir <- normalizePath(path, winslash = "/", mustWork = FALSE) dir.create(path) existing.dir <- normalizePath(path, winslash = "/", mustWork =

Hello, I discovered a bug or undocumented behavior in normalizePath steps to reproduce: execute normalizePath on a folder link on windows. When you are on a non-english windows box, you likely have links in place for windows' default folders, e.g. "C:\Programme" linking to "C:\Program Files" on german windows boxes. Thus executing

The packages "readxl" and "haven" (and possibly others) no longer access files on shared network drives. The problem appears to be in the normalizePath() function. The file can be read from a local drive or by functions that don't call normalizePath(). The error thrown is Error: path[1]="\\Hzndhhsvf2/data/OCPH/EPI/BHSDM/Group/17.xls": The system cannot find the

Hi, I have a couple of new errors in our package when I check it on R 2.13-rc (r55310). The first one that's mystifying me is * checking R code for possible problems ... NOTE Error : object normalizePath is not exported by 'namespace:utils' Error : object normalizePath is not exported by 'namespace:utils' Firstly, it's strange to see NOTE and Error being used

My R_version is 2.11.1. I can?t install R packages. The error massages are following: package 'DBI' successfully unpacked and MD5 sums checked error in normalizePath(path) : path[1]="E:\R-2.11.1\library/DBI"?? -- View this message in context: http://r.789695.n4.nabble.com/A-question-of-install-R-packages-tp2327716p2327716.html Sent from the R help mailing list archive at

Dear R People: I keep getting the "Error in normalizePath(path) :" while trying to obtain the necessary packages to use with the "Applied Spatial Statistics with R" book. I turned off the Firewall (from McAfee) but am still getting the same message. Does anyone have any idea on a solution please? > sessionInfo() R version 2.11.1 (2010-05-31) i386-pc-mingw32 locale: [1]

>>>>> Evan Cortens <ecortens at mtroyal.ca> >>>>> on Thu, 17 Nov 2016 15:51:03 -0700 writes: > I wonder if this could be related to the issue that I > submitted to bugzilla about two months ago? ( > https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17159) > That is to say, could it be that it's treating the first >

Hello, sorry for not being clear enough. My problem is represented with the following code, running on OSX: mkdir ~/test ln -s ~/test ~/testlink touch ~/test/foo Rscript -e 'Sys.readlink(c("~/test/foo", "~/testlink/foo")); normalizePath(c("~/test/foo","~/testlink/foo"))' I expected `Sys.readlink` to show the same output as `normalizePath`. Also,

Dear list, I'm facing an issue with the automated documentation of a function using roxygen2. The function has a complex-valued default argument, which is picked up by roxygen2 using formals() to generate the corresponding Usage section of the Rd file. Unfortunately, it appears that formals() reformats complex numbers. Consider the example below, test <- function(a = 1+2i){} >

I found this as well. At our institution, our home directories are on network shares that are mapped to local drives. The default, it appears, is to set the location for libraries (etc) to the network share name (//computer//share/director/a/b/user) rather than the local drive mapping (H:/). Given the issue with dir.create(), this means it's impossible to install packages (since it tries to

Hi all, A problem with tests while building R. I'm packaging R for Sisyphus repository and package build environment, by design, doesn't have /etc/localtime file present. This causes failure with Sys.timeone during test run: [builder at localhost tests]$ ../bin/R --vanilla < reg-tests-1d.R > ## PR#17186 - Sys.timezone() on some Debian-derived platforms > (S.t <-

Hi, I update R from 2.10 to 2.13. Then I find soma problems when I start R. Warning infos as below: ##### Warning message: In normalizePath(c(new, .Library.site, .Library), "/") : path[1]="": No such file or directory R version 2.13.1 (2011-07-08) Copyright (C) 2011 The R Foundation for Statistical Computing ISBN 3-900051-07-0 Platform: x86_64-pc-linux-gnu (64-bit) R is

Hello together, the function `Sys.readlink` uses the system's readlink command to resolve symlink paths. On OSX/BSD the command has a different meaning than on Linux [1]. There exists the tool 'realpath', which seems suitable for the task, at least applied at the command line level [2]. It is used in `normalizePath`. I suggest (at least the latter) to * use realpath instead readlink