Displaying 20 results from an estimated 125 matches for "normalizepath".
2019 Jan 24
1
Bug or undocumented behavior in normalizePath() with file system links on windows
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 '...
2020 Mar 23
2
Inconsistant result for normalizePath on Windows
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 purpos...
2009 Jan 27
2
Package (PR#13475)
...I get the following message
trying URL 'http://www.revolution-computing.com/cran/bin/windows/contrib/2.8/sn_0.4-10.zip'
Content type 'application/zip' length 320643 bytes (313 Kb)
opened URL
downloaded 313 Kb
package 'sn' successfully unpacked and MD5 sums checked
Error in normalizePath(path) :
path[1]: The system cannot find the file specified
2014 Sep 07
2
normalizePath is sometimes very slow for nonexistent UNC paths
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 machi...
2010 Feb 18
0
install.packages, normalizePath, file permissions
...stall.packages( file.path(fp,"fgui_1.0-0.zip" ), repos=NULL)
Warning in install.packages(file.path(fp, "fgui_1.0-0.zip"), repos = NULL) :
argument 'lib' is missing: using 'p:/Rpack'
package 'fgui' successfully unpacked and MD5 sums checked
Error in normalizePath(path) :
path[1]="p:\Rpack/fgui": The system cannot find the file specified
The circumstances are difficult to reproduce. For some reason, the
system does not like "fgui" and maybe other packages. The p: drive
above is network attached and and I have read/write access. H...
2011 Apr 06
2
R CMD check for 2.13 rc
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 interchangeably here. The package is being developed by a couple of us, so I checked that there were no calls to normali...
Suggestion/opinions: add a `absolute` param to `normalizePath()` to force returning an absolute path
2020 Apr 14
4
Suggestion/opinions: add a `absolute` param to `normalizePath()` to force returning an absolute path
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 there are benefits to being able to reliably and consistently get a
full path, regardless of whether the file exist...
2020 Mar 23
0
Inconsistant result for normalizePath on Windows
Hi Jiefei,
the change in handling trailing path separators is not on purpose, but
is a byproduct of a new implementation of normalizePath, which now
handles symbolic links and normalizes case in long path names. It is not
documented what happens to trailing separators, and hence portable
programs should not depend on it. I don't think it is a property that
should be documented/specified. The behavior of normalizePath is way t...
2011 Sep 14
3
normalizePath
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 free software and comes with ABSOLUTELY NO...
2015 Mar 11
1
normalizePath output depends on existence of directory
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 = FALSE)
&g...
Suggestion/opinions: add a `absolute` param to `normalizePath()` to force returning an absolute path
2020 Apr 15
0
Suggestion/opinions: add a `absolute` param to `normalizePath()` to force returning an absolute path
The fs[1] function `fs::path_abs()` does what I believe you were
expecting `normalizePath()` to do in this case. e.g.
setwd("~")
normalizePath("foo/bar")
#> Warning in normalizePath("foo/bar") :
#> path[1]="foo/bar": No such file or directory
#> [1] "foo/bar"
fs::path_abs("foo/bar")
#>...
2009 Apr 11
0
_Possible_ work-round for normalizePath error (was Re: [Rd] Package (PR#13475))
>>> Uwe Ligges <ligges at statistik.tu-dortmund.de> 04/10/09 4:21 PM >>>
>Well, you need to ask Symantec to fix Norton, hence this is the
>wrong address.
That would not help other R users who were looking in the archives for
help with what looked like a mysterious normalizePath error, would it?
As I said, the principal intent of the posting was to point to a
possible work-round for other R users - i.e. temporarily disabling
on-access scanning in the antivirus package.
But that would have been better posted to R-help, so it's now cc'd there
with the original pos...
2016 Feb 29
3
Sys.readlink (on BSD vs Linux)
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, I think the readlink.h imported to R to be the same as from the system's `readlink` command, thus mimicking the command line difference.
Am I wrong with the l...
2016 Nov 17
2
problem with normalizePath()
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 file specified
Here's my session:
library(readxl)
library(XLConnec...
2017 May 17
3
problem running test on a system without /etc/localtime
...ironment,
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 <- Sys.timezone())
Error in normalizePath("/etc/localtime") :
(converted from warning) path[1]="/etc/localtime": No such file or
directory
Calls: Sys.timezone -> normalizePath
Execution halted
This is caused by this code:
> Sys.timezone
function (location = TRUE)
{
tz <- Sys.getenv("TZ"...
2010 May 10
3
update.packages fails with directory not found
...kages. In the series of updates, a few will succeed, then I
get a failure like
package 'mvtnorm' successfully unpacked and MD5 sums checked
package 'party' successfully unpacked and MD5 sums checked
package 'PBSmodelling' successfully unpacked and MD5 sums checked
Error in normalizePath(path) :
path[1]="c:\Program Files\R\Library/PBSmodelling": The system cannot
find the file specified
Indeed, the path is missing, though it was there when I issued the
update.packages command.
???
--
Mike Prager, NC, USA
2016 Nov 17
0
problem with normalizePath()
...iversity
403-440-6529
On Thu, Nov 17, 2016 at 2:28 PM, Laviolette, Michael <
Michael.Laviolette at dhhs.nh.gov> wrote:
> 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 file specified
>
> Here's my session:
>...
Suggestion/opinions: add a `absolute` param to `normalizePath()` to force returning an absolute path
2020 Apr 14
0
Suggestion/opinions: add a `absolute` param to `normalizePath()` to force returning an absolute path
If we are fiddling with normalizePath, having a way of not following
symlinks (otheer than ~) would be useful as well.
I had to write normalizePath2 in switchr for a specific on-the-ground need
to NOT go down all he way to physical paths on a remote compute system
because of how IT handled implementing constant pathing on top of swa...
2016 Nov 30
0
problem with normalizePath()
...d_excel("Z:/Stat tools/addrlist-4-MikeL.xls", 2) # works
-----Original Message-----
From: Martin Maechler [mailto:maechler at stat.math.ethz.ch]
Sent: Friday, November 18, 2016 3:37 PM
To: Evan Cortens
Cc: Laviolette, Michael; r-devel at r-project.org
Subject: Re: [Rd] problem with normalizePath()
>>>>> 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/bugzilla...
2011 May 31
1
how to tell if two file paths refer to the same file
...for both paths. E.g.,
> match.path(c("c:/PROGRA~1",
"c:\\temp",
"C:/Program Files/../Program Files"),
c("C:\\Program Files",
"C:\\Temp"))
[1] 1 2 1
I know about R's normalizePath() but it doesn't map all ways
of refering to a file to the same string so
normalizePath(f1) == normalizePath(f1)
is not a reliable test. E.g., with R 2.13.0 on Windows it
doesn't use a standard capitalization:
> cat(normalizePath(c("c:/Program Files",...