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
On 06/06/2019 4:19 p.m., Toby Hocking wrote:
If anybody else has this issue, please add a comment on
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17478 so we are more
likely to get R-core to address this.
Please don't encourage spam there. Add a comment if you have
information to add,
If anybody else has this issue, please add a comment on
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17478 so we are more
likely to get R-core to address this.
Thanks
Toby
On Tue, Jun 4, 2019 at 2:58 PM Pages, Herve wrote:
> On 5/31/19 08:41, Toby Hocking wrote:...
> > In my opinion inst
On 6/6/19 3:24 PM, Duncan Murdoch wrote:
On 06/06/2019 7:28 a.m., Duncan Murdoch wrote:
On 06/06/2019 6:22 a.m., Tomas Kalibera wrote:
On 6/5/19 3:49 AM, Steven Penny wrote:
Using this in my "~/.profile":
export LC_ALL=en_US.UTF-8
Yields this:
$ Rscript -e 'print(9)'
During s
On Wed, 5 Jun 2019 18:07:15 +0200
Frank Schwidom 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],
> Martin Maechler
> on Mon, 3 Jun 2019 18:14:15 +0200 writes:
> Suharto Anggono Suharto Anggono
> on Thu, 30 May 2019 14:45:22 + writes:
> Suharto Anggono Suharto Anggono
> on Thu, 30 May 2019 14:45:22 + writes:
>> Here is a patch to function 'st
On 06/06/2019 7:28 a.m., Duncan Murdoch wrote:
On 06/06/2019 6:22 a.m., Tomas Kalibera wrote:
On 6/5/19 3:49 AM, Steven Penny wrote:
Using this in my "~/.profile":
export LC_ALL=en_US.UTF-8
Yields this:
$ Rscript -e 'print(9)'
During startup - Warning message:
Setting LC_
On 06/06/2019 6:22 a.m., Tomas Kalibera wrote:
On 6/5/19 3:49 AM, Steven Penny wrote:
Using this in my "~/.profile":
export LC_ALL=en_US.UTF-8
Yields this:
$ Rscript -e 'print(9)'
During startup - Warning message:
Setting LC_CTYPE=en_US.UTF-8 failed
[1] 9
This is confusin
On Tue, Jun 4, 2019 at 5:40 PM Steven Penny wrote:
>
> Theres nothing nefarious here. It would allow people to use the R environment
> without running an installer. If someone is a new user they may want to try
> R out, and installers can be invasive as they commonly:
>
> - copy files to install d
On 6/5/19 3:49 AM, Steven Penny wrote:
Using this in my "~/.profile":
export LC_ALL=en_US.UTF-8
Yields this:
$ Rscript -e 'print(9)'
During startup - Warning message:
Setting LC_CTYPE=en_US.UTF-8 failed
[1] 9
This is confusing as the exact same environment works fine with other
On Tue, Jun 4, 2019 at 11:06 AM Iñaki Ucar wrote:
> FWIW, innoextract extracts the contents of the installer just fine.
That is great, thank you very much:
https://github.com/dscharrer/innoextract
Between this thread and others I have interacted with 14 people, and you are the
first person to po
Using this in my "~/.profile":
export LC_ALL=en_US.UTF-8
Yields this:
$ Rscript -e 'print(9)'
During startup - Warning message:
Setting LC_CTYPE=en_US.UTF-8 failed
[1] 9
This is confusing as the exact same environment works fine with other
languages:
$ python3 -c 'print(9)'
12 matches
Mail list logo
