Hi Ivan,
In my experience, if you add purl=FALSE to those chunks, it will pass the
checks. This was the default but changed/ is the default on some platforms
not others when you have error=TRUE (don't recall details).
Jisca
On Fri, 7 Jun 2024, 16:05 Tim Taylor,
wrote:
> Does this issue over i
On 6 June 2024 at 04:47, Paul Kabaila wrote:
| When I resubmitted, I didn't realise that I needed to change the version
number.
As this comes up every now and then: This is still a _soft_ requirement. CRAN
does not 'cache' what versions you used in uploads. I have often reiterated
with the same
В Fri, 7 Jun 2024 08:40:48 -0400
Vincent Carey пишет:
> I wanted to know if anyone has a way of stepping through in a CMD
> build task.
On Linux, R CMD build launches file.path(R.home('bin'), 'build'), which
is a short script. It should be possible to step into R CMD build by
doing the same thin
Does this issue over in knitr shed some additional light ...
https://github.com/yihui/knitr/issues/2338
Tim
On 07/06/2024 14:50, Ivan Krylov via R-package-devel wrote:
В Fri, 7 Jun 2024 09:10:03 +0200
"C.H." пишет:
RMarkdown vignettes are sometimes used to demonstrate errors and one
can wri
В Fri, 7 Jun 2024 09:10:03 +0200
"C.H." пишет:
> RMarkdown vignettes are sometimes used to demonstrate errors and one
> can write vignettes with `error` chunks.
>
> ```{r, error = TRUE}
> stop()
> ```
> But now CRAN also reports the same ERRORS for mac and linux `oldrel`
> (4.3.3).
>
> https:/
https://bioconductor.org/checkResults/3.20/bioc-LATEST/velociraptor/nebbiolo2-buildsrc.html
shows an error arising in R CMD build that cannot be reproduced
in manual attempts with the vignette code that is triggering the
error. "It works fine except in CMD build" (on linux).
I have tried debuggi
Dear all,
RMarkdown vignettes are sometimes used to demonstrate errors and one
can write vignettes with `error` chunks.
```{r, error = TRUE}
stop()
```
This was not an issue for a long time. But I've experienced sometimes
in the past that packages with these vignettes going through `R CMD
check`
On Thu, 6 Jun 2024, Iris Simmons wrote:
Unless I'm misunderstanding, you're trying to pass a value by name to a
function. That is not a thing in C nor C++. However if you want to name the
arguments, you can do so with comments:
/* print = */ print
I would recommend against using comments i
