Re: [Rd] force promises inside lapply

Thanks Bill. I think my confusion may have been in part due to my conflating two distinct meanings of the term "evaluate"; the help for force says it "forces the evaluation of a function argument" whereas the help for eval says it "evaluates the ... argument ... and returns the computed

[R-pkg-devel] Problems runing a example (shiny App) within a package

Problems running a example (shiny App) within a package #main code runclt = function(){ shiny::runApp(system.file("shinyCLT", package="CLT")) } #example \examples{ runclt() } #Problem R CMD check breaks in "checking examples ..." and don't complete the tests. How to solve it

Re: [Rd] force promises inside lapply

1: substitute(), when given an argument to a function (which will be a promise) gives you the unevaluated expression given as the argument: > L <- list(a=1, b=2, c=3) > str(lapply(L, function(x) substitute(x))) List of 3 $ a: language X[[i]] $ b: language X[[i]] $ c: language X[[i]] The 'X'

[Rd] force promises inside lapply

Hi, I thought I understood the change to lapply semantics resulting from this, https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16093 However, would someone care to explain why this does not work? > L <- list(a=1, b=2, c=3) > str(lapply(L, function(x){ y <- substitute(x);

[Rd] I have corrected a dead link in the treering documentation

The attached patch corrects a dead link in the treering documentation. The URL in the manual [1] refers to a personal home page belonging to Christine Hallman (user "hallman") on the website of the University of Arizona Laboratory of Tree-Ring Research (LTRR). It seems that the LTRR personal

Re: [Rd] Problems with S4 methods dispatching on `...` (aka dotsMethods)

I pushed the patch to the 3.4 branch. Feel free to test. Michael On Wed, Jul 26, 2017 at 4:02 AM, Andrzej Oleś wrote: > Hi Michael, > > it seems that your patch to S4 generics dispatching on `...` is still > available only in R-devel, and was not included in the minor

Re: [Bioc-devel] git transition for projects with prior git history

Hi Nitesh, Schematically, my git repo started with commit D, while bioconductor's started with A. It's possible this was because I did something wrong managing the bioconductor repo, but since I can't rewrite history, there's not anything I can do about that now. Their "founding" commits are

Re: [Bioc-devel] git transition for projects with prior git history

I would be careful before using the --allow-unrelated-histories flag. Please investigate where there is a difference. Also, i don't understand why you are using the bioconductor-git-mirror? Your non-zero commit history should be related to bioconductor git server. Best Nitesh Get Outlook for

Re: [Bioc-devel] Catching SVN up to Github

It seems like you renamed your package after it was submitted based on the current version in svn and the current ERROR occurring on the build report. Could you check your git config -l and see if the svn-remote* in the config file are updated to reflect the naming change? Lori Shepherd

Re: [R-pkg-devel] Seamless way for a CRAN-bound package to depend on a Bioconductor package?

On 28 July 2017 at 12:42, Pavel Krivitsky wrote: | Dear All, | | There is a Bioconductor package (S4Vectors) whose functionality I want | to use in one of my packages, which I usually submit to CRAN. | | At this time, install.packages() does not automatically fetch | dependencies from

[R-pkg-devel] Seamless way for a CRAN-bound package to depend on a Bioconductor package?

Dear All, There is a Bioconductor package (S4Vectors) whose functionality I want to use in one of my packages, which I usually submit to CRAN. At this time, install.packages() does not automatically fetch dependencies from Bioconductor as far as I can tell, though it can be told to do so via

Re: [Rd] Issue with memory deallocation/fragmentation on systems which use glibc

I would like to submit issue to wishlist at the bug reporting system ( https://www.r-project.org/bugs.html) based on my emails. Unfortunately I don't have bugzilla account. Can someone from R-core help to obtain it? (I see that I should *"ask an R Core member to add you manually to R’s Bugzilla