search for: r_expandfilename_readline

...; 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 [4], which uses libreadline function tilde_expand [5]. tilde_expand seems to be designed to expand '~' anywhere in the string it is handed, i.e. operate on whole command lines, not file paths. I am taking the liberty of Cc-ing R-devel in case this can be considered a bug. -- Best regards...

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

.../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 [4], which uses libreadline function >> tilde_expand [5]. tilde_expand seems to be designed to expand '~' >> anywhere in the string it is handed, i.e. operate on whole command >> lines, not file paths. >> >> I am taking the liberty of Cc-ing R-devel in case th...

...y? > > > > > > > > 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 [4], which uses libreadline > function > > > > tilde_expand [5]. tilde_expand seems to be designed to expand > '~' > > > > anywhere in the string it is handed, i.e. operate on whole > command > > > > lines, not file paths. > &gt...

...;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 [4], which uses libreadline function >> tilde_expand [5]. tilde_expand seems to be designed to expand '~' >> anywhere in the string it is handed, i.e. operate on whole command >> lines, not file paths. >> >> I am taking the liberty of Cc-ing R-devel in case thi...

...~ 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 [4], which uses libreadline function > tilde_expand [5]. tilde_expand seems to be designed to expand '~' > anywhere in the string it is handed, i.e. operate on whole command > lines, not file paths. > > I am taking the liberty of Cc-ing R-devel in case this can be > consid...

...itch 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 [4], which uses libreadline function > > > tilde_expand [5]. tilde_expand seems to be designed to expand '~' > > > anywhere in the string it is handed, i.e. operate on whole command > > > lines, not file paths. > > > > > > I a...

...>>> 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 [4], which uses libreadline function > >> tilde_expand [5]. tilde_expand seems to be designed to expand '~' > >> anywhere in the string it is handed, i.e. operate on whole command > >> lines, not file paths. > >> > >> I am taking the liberty of C...

...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 [4], which uses libreadline function >>>> tilde_expand [5]. tilde_expand seems to be designed to expand '~' >>>> anywhere in the string it is handed, i.e. operate on whole command >>>> lines, not file paths. >>>> >>>> I am taking t...

...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 [4], which uses > libreadline > > function > > > > > tilde_expand [5]. tilde_expand seems to be designed to > expand > > '~' > > > > > anywhere in the string it is handed, i.e. operate on > whole > >...

...line is enabled and >>>> works >>>> > > > correctly. >>>> > > > >>>> > > > Calls to path.expand [1] end up [2] in R_ExpandFileName >>> [3], >>>> which >>>> > > > calls R_ExpandFileName_readline [4], which uses >>> libreadline >>>> function >>>> > > > tilde_expand [5]. tilde_expand seems to be designed to >>> expand >>>> '~' >>>> > > > anywhere in the string it is handed, i.e. operate on &...

...;>> > > > correctly. > > >>>> > > > > > >>>> > > > Calls to path.expand [1] end up [2] in R_ExpandFileName > > >>> [3], > > >>>> which > > >>>> > > > calls R_ExpandFileName_readline [4], which uses > > >>> libreadline > > >>>> function > > >>>> > > > tilde_expand [5]. tilde_expand seems to be designed to > > >>> expand > > >>>> '~' > > >>>> > > >...

...t; >? ? ? 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 [4], which uses libreadline > function > > > >? ? ? tilde_expand [5]. tilde_expand seems to be designed to expand > '~' > > > >? ? ? anywhere in the string it is handed, i.e. operate on whole > command > > > >? ? ? l...

...enabled and >>> works >>> > > > correctly. >>> > > > >>> > > > Calls to path.expand [1] end up [2] in R_ExpandFileName >> [3], >>> which >>> > > > calls R_ExpandFileName_readline [4], which uses >> libreadline >>> function >>> > > > tilde_expand [5]. tilde_expand seems to be designed to >> expand >>> '~' >>> > > > anywhere in the string it is handed, i.e. operate on &...

...t;> works > >>>> > > > correctly. > >>>> > > > > >>>> > > > Calls to path.expand [1] end up [2] in R_ExpandFileName > >>> [3], > >>>> which > >>>> > > > calls R_ExpandFileName_readline [4], which uses > >>> libreadline > >>>> function > >>>> > > > tilde_expand [5]. tilde_expand seems to be designed to > >>> expand > >>>> '~' > >>>> > > > anywhere in the string i...

...> correctly. >> > >>>> > > > >> > >>>> > > > Calls to path.expand [1] end up [2] in R_ExpandFileName >> > >>> [3], >> > >>>> which >> > >>>> > > > calls R_ExpandFileName_readline [4], which uses >> > >>> libreadline >> > >>>> function >> > >>>> > > > tilde_expand [5]. tilde_expand seems to be designed to >> > >>> expand >> > >>>> '~' >> > >&gt...