anmarco Alberti
> > Sent: 08 July 2021 08:21
> > To: r-package-devel@r-project.org
> > Cc: Murray Efford; Duncan Murdoch; Alex Chubaty; Uwe Ligges
> > Subject: Re: [R-pkg-devel] package test returns error when R version
> 4.1.0
> >
> > Dear All,
> > Than
tart cutting out code and data. Etc.
>
> In any case, try to find a version of the package that doesn't trigger
> the error, and a minimal change to it that does. Then perhaps you'll
> understand the root cause of the error.
>
> Duncan Murdoch
>
> On 06/07/2021 3:11 p
FWIW I'm having the same issue with package NetLogoR (
https://github.com/PredictiveEcology/NetLogoR/)
Passing windows tests locally but code can't be lazy loaded on winbuilder,
except for oldrel.
Alex
On Tue, Jul 6, 2021 at 10:18 AM Gianmarco Alberti <
gianmarcoalbe...@gmail.com> wrote:
>
During a recent package submission process, a CRAN maintainer showed one of
their checks found missing \value{} documentation in some package Rd files,
and asked us to ensure all exported functions have their return values
described.
This check (for missing Rd values) is not run by the default che
Thank you Martin for passing this along to RStudio, and thank you JJ for
your reply.
JJ, do you have an estimated timeframe for when this fix will appear?
There's still the issue of RStudio users not updating their software at
each and every release, so it may time some time for `dev.new` to work
Dear list members,
Use of platform-specific code to open new plot devices (e.g., `quartz`,
`x11`) is discouraged in favour of using `dev.new`; however, this does not
work in RStudio. A purported solution introduced in R 3.1.1 was to call
`dev.new(noRStudioGD = TRUE)`, which works on Windows, but n
