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

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 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

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

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

?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

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

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

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

@ 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

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

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 John, First, the unix and linux filesystem allows the use of any nonzero character in its filesystem filenames and the c functions open / fopen, symlink. rename, chdir and so on don't care about any tilde. If the open systemcall gets a file which begins with a tilde then it will try to open this filename without any preceding modification. So the tilde expansion is not really a unix

https://bugzilla.mindrot.org/show_bug.cgi?id=2481 Bug ID: 2481 Summary: Tilde expansion in -i option inconsistent Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: Linux Status: NEW Severity: trivial Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org

On Mon, 17 Aug 2015, Todd C. Miller wrote: > I like the idea but tilde_expand_filename() calls fatal() if it > cannot resolve ~foo. This is not terrible when using -L and -R on > the normal command line but it seems pretty harsh to exit when -L > or -R are used via the ~C escape or the streamlocal-forward at openssh.com > request. > Message-Id: <aea6cdc1d1b42d07 at

On 11/15/2017 06:54 AM, Holger Schranz wrote: > Thread 1 (Thread 0x7f4a069cc700 (LWP 10178)): > #0 0x00007f49ff969170 in qemuDomainChangeEjectableMedia ( > driver=driver@entry=0x7f49f841b700, vm=vm@entry=0x7f49ec02fbd0, > disk=disk@entry=0x7f49ec0375d0, newsrc=0x7f49e8014d10, force=force@entry=false) > at qemu/qemu_hotplug.c:303 This is fixed in current upstream by