[Rd] odd behavior of names

The first component name has backticks around it and the second does not. Though not wrong, it seems inconsistent. list(a = 1, b = 2) ## $`a` ## [1] 1 ## ## $b ## [1] 2 R.version.string ## [1] "R version 3.5.1 Patched (2018-07-02 r74950)" -- Statistics & Software Consulting GKX Group, GKX Ass

Re: [Rd] odd behavior of names

> On Jul 29, 2018, at 6:31 AM, Gabor Grothendieck > wrote: > > The first component name has backticks around it and the second does > not. Though not wrong, it seems inconsistent. > > list(a = 1, b = 2) > ## $`a` > ## [1] 1 > ## > ## $b > ## [1] 2 > > R.version.string > ## [1] "R version 3.5

Re: [Rd] odd behavior of names

Bugzilla issue 16101 describes another first-list-name-printed-differently oddity with the Windows GUI version of R: > a <- "One is \u043E\u0434\u0438\u043D\nTwo is \u0434\u0432\u0430\n" > Encoding(a) # expect "UTF-8" [1] "UTF-8" > sapply(strsplit(a, "\n")[[1]], charToRaw)[c(1,1,2)] $`One is один`

Re: [Rd] Possible To Enable Building R With Cairo But Without X11 Dependencies?

Thanks for the reply, Dirk. It sounds like xvfb-run is a great solution when you want R to assume an X window system is present but isn’t? I think what I'm trying to figure out, and propose for the community to possibly fix, is slightly different than would be solved by xvfb-run. I'm wondering i

[Rd] apply with zero-row matrix

Forgive me if this has been asked many times before, but I couldn't find anything on the mailing lists. I'd expect apply(m, 1, foo) not to call `foo` if m is a matrix with zero rows. In fact: m <- matrix(NA, 0, 5) apply(m, 1, function (x) {cat("Called...\n"); print(x)}) ## Called... ## [1] FALSE

[Rd] Fwd: help building very old R

Hi guys, Perhaps someone here can help. I am trying to build versions of R 1 for the rcheology package (just arrived on CRAN). For R prior to 1.5.0, I cannot configure support for tcl-tk. I am building on Debian Woody (provided by Docker debian/eol) and have the following packages installed: r-