similar to: [R] Open a file which name contains a tilde

@ Gabriel: "Avoid tilde in file names": Not quite. A tilde *suffix* is commonly used by *nix editors for backup files https://unix.stackexchange.com/questions/76189/what-does-the-tilde-mean-at-the-end-of-a-filename On Wed, Jun 12, 2019 at 2:43 AM Kurt Hornik <Kurt.Hornik at wu.ac.at> wrote: > >>>>> Duncan Murdoch writes: > > With c76695 in the trunk, we

Hi Gabriel, I actually want to make renames over thousands of files. But if I am not able to express the source filename of the rename operation I will not be able to get the work done. Besides the fact that there are issues I think that R is qualified for solving my problem by the method how it can handle long vectors of strings, booleans and also lists. Kind regards, Frank On 2019-06-11

On 11/06/2019 4:34 p.m., William Dunlap via R-devel wrote: > Note that R treats tildes in file names differently on Windows and Linux. > On Windows, it is only replaced if it it at the beginning of the line and > is followed by a forward or backward slash or end-of-line. On Linux it is > replaced no matter where it is in the text and ~someUser will be replaced > by someUser's

At the risk of looking silly, note that all of this is now largely moot anyway (or will be with the next release of R), thanks to Kurt Hornik's fixing of the bug in question (which he announced on this thread prior to but I read after Paul's). ~G On Wed, Jun 12, 2019 at 11:51 PM Gabriel Becker <gabembecker at gmail.com> wrote: > > > On Wed, Jun 12, 2019, 5:16 AM Paul

Hi, yes, I have seen this package and it has the same tilde expanding problem. Please excuse me I will cc this answer to r-help and r-devel to keep the discussion running. Kind regards, Frank Schwidom On 2019-06-11 09:12:36, G?bor Cs?rdi wrote: > Just in case, have you seen the fs package? > https://fs.r-lib.org/ > > Gabor > > On Tue, Jun 11, 2019 at 7:51 AM Frank Schwidom

?path.expand Expand a path name, for example by replacing a leading tilde by the user's home directory (if defined on that platform). *A* path name. The argument is a character vector. If multiple path names are passed, they are passed On most builds of R *A LEADING* "~user" will be replaced... Nothing is said in the R documentation about *multiple* or *non-leading*

Hello, R 3.6.0 on Ubuntu 19.04. Since no one mentioned it, notice that the tilde in the middle of a string needs to be surrounded by spaces to be expanded. The first code line works as expected, only the second is wrong (buggy). path.expand('a~b') #[1] "a~b" path.expand('a ~ b') #[1] "a /home/rui b" Rui Barradas ?s 04:27 de 08/06/19, Richard O'Keefe

Note that R treats tildes in file names differently on Windows and Linux. On Windows, it is only replaced if it it at the beginning of the line and is followed by a forward or backward slash or end-of-line. On Linux it is replaced no matter where it is in the text and ~someUser will be replaced by someUser's home directory (if 'someUser' is a user with a home directory). Hence, if

>>>>> Duncan Murdoch writes: With c76695 in the trunk, we now only tilde expand file names starting with a tilde also when using readline. Best -k > On 11/06/2019 4:34 p.m., William Dunlap via R-devel wrote: >> Note that R treats tildes in file names differently on Windows and Linux. >> On Windows, it is only replaced if it it at the beginning of the line and

On Wed, Jun 12, 2019, 5:16 AM Paul McQuesten <mcquesten at gmail.com> wrote: > @ Gabriel: > > "Avoid tilde in file names": > Not quite. > A tilde *suffix* is commonly used by *nix editors for backup files > > https://unix.stackexchange.com/questions/76189/what-does-the-tilde-mean-at-the-end-of-a-filename I'm aware of that, but that isn't the case

On 06/06/2019 5:04 p.m., Richard O'Keefe wrote: > How can expanding tildes anywhere but the beginning of a file name NOT be > considered a bug? It looks like a bug in R, but not necessarily a bug in libreadline: we may just be using tilde_expand improperly. Duncan Murdoch > > > On Thu, 6 Jun 2019 at 23:04, Ivan Krylov <krylov.r00t at gmail.com> wrote: > >>

How can expanding tildes anywhere but the beginning of a file name NOT be considered a bug? On Thu, 6 Jun 2019 at 23:04, Ivan Krylov <krylov.r00t at gmail.com> wrote: > On Wed, 5 Jun 2019 18:07:15 +0200 > Frank Schwidom <schwidom at gmx.net> wrote: > > > +> path.expand("a ~ b") > > [1] "a /home/user b" > > > How can I switch off

Hi Frank, I'm hesitant to be "that guy", but in case no one else has brought this up to you, having files with a tilde in their names (generally but especially on a linux system, where ~ in file names has a very important special meaning in some cases, as we know) strikes me as an exceptionally bad practice anyway. In light of that, the solution with the smallest amount of pain for

> On Jun 6, 2019, at 2:04 PM, Richard O'Keefe <raoknz at gmail.com> wrote: > > How can expanding tildes anywhere but the beginning of a file name NOT be > considered a bug? > > I think that that IS what libreadline is doing if one allows a whitespace separated list of file names. As reported in R-help, https://www.mail-archive.com/r-help at

On Wed, 5 Jun 2019 18:07:15 +0200 Frank Schwidom <schwidom at gmx.net> wrote: > +> path.expand("a ~ b") > [1] "a /home/user b" > How can I switch off any file crippling activity? It doesn't seem to be possible if readline is enabled and works correctly. Calls to path.expand [1] end up [2] in R_ExpandFileName [3], which calls R_ExpandFileName_readline

Hi, As I can see via path.expand a filename which contains a tilde anywhere gets automatically crippled. +> path.expand("a ~ b") [1] "a /home/user b" +> path.expand("a ~ b ~") [1] "a /home/user b /home/user" I want to open a file regardless whether its name contains any character unless 0. The unix filesystem allow the creation of such files, it

Hi, As I can see via path.expand a filename which contains a tilde anywhere gets automatically crippled. +> path.expand("a ~ b") [1] "a /home/user b" +> path.expand("a ~ b ~") [1] "a /home/user b /home/user" I want to open a file regardless whether its name contains any character unless 0. The unix filesystem allow the creation of such files, it

I've reproduced on ubuntu and winodws with R3.4.3 When the filepath contains a tilde, the result is NA. But if the file path is expanded then the function works. Example: tools::md5sum("~/.Rprofile") returns NA tools::md5sum(normalizePath("~/.Rprofile")) returns the proper md5 Perhaps this is expected behaviour because the documentation does say NA is returned for

Suppose I have a plot plot(1:10, pch = "") And I want some text to indicate a Normal distrubition. I could do this: text(5, 6, substitute(X~~~~N(mu, sigma^2)), adj = 0) text(5.35, 6, "~", adj = 0) But that's clumsy, and depending on your plotting device, might not even look sensible. I'd prefer to be able to do it more directly and simply the way these do: text(5,

Commit-ID: 91d0712951d61680da0e26aa356787b80b7368d8 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=91d0712951d61680da0e26aa356787b80b7368d8 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sun, 27 May 2018 17:31:57 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: expand: Use