search for: tilde_expand

..."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, Ivan [1] https://github.com/wch/r-source/blob/1...

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

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

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: > >> On Wed, 5 Jun 2019 18:07:15 +0200 >> Frank Schwidom <schwidom at gmx.net> wrote: >> >>> +> path.expand("a ~ b") >&...

...g* tildes being replaced. The actual behaviour is inconsistent with the documentation. SOMETHING is a bug. It's not clear to me why this is in any way dependent on readline. I've implemented tilde expansion several times and always without readline. It sounds as though R might be calling tilde_expand() when it *should*, to be consistent with the documentation, be calling tilde_expand_word(). as separate elements of the character vector. On Sat, 8 Jun 2019 at 04:10, Berry, Charles <ccberry at ucsd.edu> wrote: > > > > On Jun 6, 2019, at 2:04 PM, Richard O'Keefe <ra...

...actual behaviour is inconsistent with the documentation. > SOMETHING is a bug. > > It's not clear to me why this is in any way dependent on > readline. I've implemented tilde expansion several times > and always without readline. > It sounds as though R might be calling tilde_expand() > when it *should*, to be consistent with the documentation, > be calling tilde_expand_word(). > > > > as separate elements of the character vector. > > > > On Sat, 8 Jun 2019 at 04:10, Berry, Charles <ccberry at ucsd.edu> wrote: > >> >> &...

...e 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 i...

...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, > Ivan &...

Specifically Solaris 2.7 and R 1.2.2 patched, but the principle is general. src/unix/sys-unix.c declares the function tilde_expand from readline, incorrectly for readline 4.x. That's OK in 4.1 as it is not in the included headers, but it is for 4.2, and so compilation fails (under gcc 2.95.3 at least). The quick fix is (ca line 88) char *tilde_expand(const char*); ^^^^^ but we should really check the...

...39;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 > > &...

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

...;>> > > > 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. >>>&g...

...p [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 > > >>>&g...

...t; > >? ? ? 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...

...gt; > > > 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. >>>...

...rc/library/base' building package 'base' /bin/sh: /usr/bin/cat: 0403-027 The parameter list is too long. If unfixed, I get errors like: Error: couldn't find function "attach" (fix: put the source directory somewhere down the tree - e.g. I symlinked it to /tmp/R ;)). 3) tilde_expand from readline: "/.../dce.uni-augsburg.de/fs/home/mathe/sta/urbanesi/work/R-1.8.0/src/ unix/sys-unix.c", line 103.14: 1506-196 (S) Initialization between types "char*" and "int" is not allowed. fix: add a corresponding declaration for tilde_expand 4) .so vs .a ld: 0...

...ecially if no one knows about them. > Let me pass that on to R Bugs then as it is in no way related to any Debian > changes. > > Thanks, Dirk > > > | looking at /usr/lib/R/bin/INSTALL, the problem seems to be in the block starting at line 298: > | > | > | > | lib=`tilde_expand "${lib}"` > | if test -z "${lib}"; then > | lib=`echo "cat('\n~~~', .libPaths()[1], '\n', sep = '')" | \ > | R_DEFAULT_PACKAGES=NULL "${R_EXE}" --no-save --slave | \ > | grep '^~~~' | sed 's/.*~~~//...

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

...e >> > >>> [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 >...