Displaying 2 results from an estimated 2 matches for "normalizepath2".
Did you mean:
normalizepath
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 swapping
out hardware, and I can't imagine i'm the only one who has ever faced such
an issue.
~G
On Tue, Ap...
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