similar to: readline 4.2 shows R has (fatal) incorrect declarations. (PR#913)

Several folks have previously written that valgrind notices a memory leak in R's readline code. It looks like it leaks a copy of every input line. % ~/R-svn/r-devel/R/bin/R --debugger=valgrind --debugger-args=--leak-check=full --vanilla ==10725== Memcheck, a memory error detector. ==10725== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. ==10725== Using LibVEX rev 1658, a

I looked for evidence that this is supposed to happen, as it was news to me that it did on some versions of R. Possible sources of documentation seem to be R CMD INSTALL --help ?INSTALL R-intro.texi, R-exts.texi, R-admin.texi none of which mention this AFAICS, and all seem to be written assuming an existing library tree. DId you find something to suggest otherwise? Clearly no alpha/beta

Based on a report to the Windows maintainers from Richard Rowe <Richard.Rowe@jcu.edu.au>: NEWS for 1.3.0 says o Exact p-values are available for the two-sided two-sample Kolmogorov-Smirnov test. I think the (new) p-values are computed but are backwards: > set.seed(123) > x <- rnorm(50) > y <- runif(50) > ks.test(x,y, exact=T)$p [1] 1 > 1 - ks.test(x,y,

?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

There is a bug in the command-line handling of 0.65.0 under Unix that may affect some users of R-inferior-mode under ESS, as that sets --no-readline as the first argument, and any arguments after that are ignored. The fix is simple: delete line 448 of src/unix/sys-common.c (`break;') and re-compile. The most used arguments are (I'm told) --vsize and --nsize. I find it more convenient to

On Fri, 17 May 2002 Ray.Brownrigg@mcs.vuw.ac.nz wrote: > Firstly I omitted the following information from my original message: > > R is now configured for i386--netbsdelf > > Source directory: . > Installation directory: /usr/pkg > C compiler: cc -mieee-fp -I/mnt/scratch/pkgsrc/math/R/work.i386/.buildlink/include -O2

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 Mon, 20 May 2002 dciemo@excite.com wrote: > Full_Name: David Ciemiewicz > Version: 1.3.1 > OS: Windows 2000 > Submission from: (NULL) (63.192.218.208) > > > In the R Language Manual (R-lang.pdf), section 3.2.1 "if", there is an example > expression which uses the function "any". > > > if( any(x) <= 0 ) y <- log(1+x) else y <- log(x)

> 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

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

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

Using zero-weight values in glm returns incorrect fitted values and linear predictors, the ninth value in the following. > example(glm) > fit <- glm(counts ~ outcome + treatment, family = poisson(), data=d.AD, weights=c(rep(1,8), 0)) > fit$linear.predictor 1 2 3 4 5 6 7 8 2.989646 2.535391 2.862201 2.989646

On Wed, 20 Dec 2000 joehl@web.de wrote: > > # creating a file > > cat("sddfasdf", file="tempfile") > > showConnections() > class description mode text isopen can read can write > > con <- file("tempfile", "r") > > readLines(con) > [1] "sddfasdf" > Warning message: > incomplete final line in:

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

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

syskern (`Functions for writing code that is OS and R/S independent', an amazing description given the reality) fails Rcmd check on Windows, and also gives incorrect information where it does work. There are already correct OS-independent functions for these purposes in R. It appears not to be needed to run the other three packages in the dse bundle, but to be the only R package that

@ 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

This does seem to fix my problem: > Sys.getenv("http_proxy") http_proxy "http://gproxy1.pfizer.com/" > url("http://cran.r-project.org/src/contrib/PACKAGES",'r') description "http://cran.r-project.org/src/contrib/PACKAGES" class