similar to: objects intermittently shared between vignettes

Hello: Clicking "Knit Word" in RStudio 0.99.893 with R 3.3.0, works fine with a vignette with "output: word_document". However, "R CMD build" throws the following error: $ R CMD build pkgW2vignettes * checking for file ?pkgW2vignettes/DESCRIPTION? ... OK * preparing ?pkgW2vignettes?: * checking DESCRIPTION meta-information ... OK * installing the

If I understand correctly, all vignettes in a package are built in the same R process. Global options, loaded packages, etc., in an earlier vignette persist in later vignettes. This can introduce user confusion (e.g., when a later vignette builds successfully because a package is require()'ed in an earlier vignette, but not the current one), difficult-to-identify bugs (e.g., when a setting

Dear R-devel list, My name is Guillermo Vinu?. I have created an R package that includes a vignette. Earlier on, to test my package, I tried to install it both in Linux and Windows and it worked. My vignette was in /inst/doc. Now, I have finished for good and before submitting my package to CRAN I've tried to install it again first in Linux and then in Windows (I removed that first

As a user, I am always annoyed beyond measure that Sweave vignettes precede the code by a command line prompt. It makes running examples by simple copying of the commands from the vignette to the console a pain. I know the idea is that it is clear what is the command, and what is the output, but I'd rather precede the output with some kind of marking. Is there any other solution possible /

Hello, The vignette concept, which started in Bioconductor, seems to be catching on. They are supported by R CMD build/check and documented in the Writing R Extensions manual. I think vignettes are a fantastic way to introduce new users to a package. However, getting new users to realize that a vignette is available can be challenging. For some time now, we have had a function in Biobase that

A new problem has cropped up with compiling vignettes for my package BayesFactor. I'm not sure when it started, but I can tell you it didn't occur on R 2.15.3, and it does on 3.0.0 RC (2013-03-31 r62463) (session info is at the bottom of this message). I have defined methods for which.min and which.max for a class (I've defined both S3 and S4 methods for the class

Dear all, I am struggling with an issue related to static vignettes: they work, but only when present in double in the tarball -- in the folder inst/doc and vignettes; see below for details. Details: I am pre-compiling heavy vignettes thanks to the vignette builder R.rsp. So basically, I have PDF files which I want the package to use as Vignettes. For this, I have the following in my

Is there a way to include the compiled version of a vignette in the doc directory but mark it to NOT be rerun by CRAN??? I think I remember that this is possible, but have forgotton how.?? (It might even be a false memory.) Terry T. Background:? Beth Atkinson and I are splitting out many of the vignettes from the survival package into a separate package survivalVignettes.? There are a few

I was recently browsing through CRAN's Finance task view to remind myself of the publicly available packages relevant to my work. As the reference manuals are all online, I am able to flip through the available functions to get an idea of the package's scope before downloading. That said, many authors have taken the time to additionally provide a useful vignette which provides a better

On 01/11/2020 2:57 p.m., Dirk Eddelbuettel wrote: > > The closest to a canonical reference for a static vignette is the basic blog > post by Mark at > > https://www.markvanderloo.eu/yaRb/2019/01/11/add-a-static-pdf-vignette-to-an-r-package/ > > which I follow in a number of packages. > > Back to the original point by Alexandre: No, I do _not_ think we can do >

I am looking for a way to generate .Rout.save files for vignettes. The manual "Writing R Extensions" states here [1] in item number 20: "If there is a target output file .Rout.save in the vignette source directory, the output from running the code in that vignette is compared with the target output file." Yet, there is no pointer on how to get the correct .Rout.save files

In R 3.1.0 (~April 2014), support for vignettes in inst/doc/ will go away (and probably much sooner for CRAN submission), e.g. checking for old-style vignette sources ... NOTE Vignette sources only in ?inst/doc?: ?R.devices-overview.tex.rsp? A ?vignettes? directory is required as from R 3.1.0 and these will not be indexed nor checked I've been sticking with inst/doc/ for backward compatible

Hi, is it possible to have non-Sweave vignettes(*) in inst/doc/ be listed under 'Downloads' on CRAN package pages? For instance, in my R.rsp package I have a inst/doc/report.pdf (part of the source *.tar.gz) that is not detected/listed. The PDF is not based on a Sweave vignette but an *.tex.rsp vignette that is dynamically created via inst/doc/Makefile. It is listed (*) BTW, can the

In R 3.0.2 Patched (2014-01-31 r64905) and 3.0.3 beta (2014-02-25 r65077) I see a problem loading vignettes when I create a package with two vignettes with similar names, e.g. "vignette3" "vignette3-install" These seem not to be distinguished, and I get this vignette("vignette3") vignette ?vignette3? not found vignette("vignette3-install") Warning

In a package I'm working on there is a vignette with a number of graphs that result in huge .pdf files, so the .pdf for the vignette is around 17 Mb. If these graphs are converted to .png, and the .tex file is compiled with pdflatex, the resulting .pdf is ~1 Mb. I'm reluctant to put the .Rnw file into the package as is, generating the huge .pdf for the vignette. I first tried

Noted Duncan and TRUE... I cannot do more immediately unfortunately, that is always the issue of asking a last minute panic attack question before teaching a course involving the package... I do have /doc in my .Rbuildignore for reasons I can no longer remember... I will dig and create a MRE/reprex. The students will download heavy packages, but they probably won't notice. *Apologies* In the

Hello, I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31)) that has not seen any changes since it was last built without problems in previous R versions. It fails during vignette building with: ---<--------------------cut here---------------start------------------->--- $ R CMD build diveMove * checking for file ?diveMove/DESCRIPTION? ... OK * preparing ?diveMove?: *

Dear Community, I have an Rmarkdown vignette with optional child documents. Since all markdown files in the vingette folder are build when executing R CMD build I did place the child documents in /inst/ParametrizedReportChid/ so they are excluded from the build. I do reference them from the markdown file in the vignette folder by: ```{r referencingChildDocument} child_docs <-

Hi, as far as I understand it, the new R devel feature of processing non-Sweave vignettes will (a) locate any "[.][RrSs](nw|tex)$" or ".Rmd" files, (b) check for a registered vignette engine, (c) process the file using the registered "weave" function, (d) and possibly post process the generated weave artifact (e.g. a *.tex file). I'd like to propose to extend

In a package 'vig' R CMD build vig (or tools::buildVignettes(dir="vig") with $ cat vig/vignettes/vig1.Rnw \documentclass{article} \begin{document} <<>>= x <- 1 @ \end{document} $ cat vig/vignettes/vig2.Rnw \documentclass{article} \begin{document} <<>>= x @ \end{document} produces vig2.pdf where x is defined with value 1 -- the vignettes share a build