similar to: CRAN: How to list a non-Sweave doc under "Vignettes:" on package page?

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

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 /

Now that R 3.0.0+ supports non-Sweave vignettes, R-exts \S 1.4.2 seems to imply that it is possible to include both Sweave and knitr vignettes in a single package. I'm wondering if anyone has tried this and/or if there are some hidden gotchas putting this into practice, and concerned about creating problems with CRAN checks if I try this. Consider two vignettes: pkg/vignettes/vign1.Rnw,

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, 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 ?Sweave, it refers to Sweave User Manual. In the doc folder of utils package, I see "Sweave.pdf". However, I can't find it from within R > vignette("Sweave User Manual") Warning message: vignette ?Sweave User Manual? not found > browseVignettes("utils") No vignettes found by browseVignettes("utils") > library(help=utils) does not

During vignette generation on Windows, Sweave seems to clean up before all graphics files are completely processed. For instance, if tmp.Rnw is: \documentclass[12pt]{article} \begin{document} <<>>= bitmap("afile.png") plot(1:100) dev.off() @ \end{document} Then: C:\R\tmp>R CMD Sweave tmp.Rnw Writing to file tmp.tex Processing code chunks ... 1 : echo term verbatim

It is stated in R-exts that Sweave files (.Rnw) are either processed in /vignettes or /inst/doc, not both. Furthermore, it is stated that external manuals and other files in /inst/doc will be installed. This behaviour has been used to deal with the situation where a package has two "vignettes", one that is easily processed and one that has a long running time. This could be done by

Dear R-devel, Question: How can I get Sweave to recognize that the \thebibliography section is already created and generate the vignette pdf with a single pass? Or is there a way to let R CMD build know that Sweave needs to be run twice? If (1) is not possible, any suggestions how to auto-generate a crude generic bibtex .bib file from my existing document? Background: I maintain

Trying to Stangle / Sweave a file $ cat vignette.Rnw %\VignetteEngine{knitr} \documentclass{article} \begin{document} \end{document} results in a misleading error message: ~/tmp$ R CMD Stangle vignette.Rnw Error: Vignette engine package not specified Execution halted when what is missing is the full specification knitr::knitr; 'vignette engine package and function not specified' ?

Currently Makefiles for vignettes are only supported for .tex files. Could the tools package be modified to allow file extensions to be specified for a vignette engine? Having the pandoc pdf conversion in a Makefile rather than through R would be tidier in some cases. If I specify my vignette engine as ``` tools::vignetteEngine( 'myengine', pattern = '\\.[Rr](md|nw)$',

I haven't figured it out entirely, but it looks like there are a couple of small glitches with knitr-based vignettes and SweaveParseOptions. I posted the tarball of a package with a knitr vignette with (as far as I can tell) everything properly coded in the DESCRIPTION file (VignetteBuilder: knitr, Suggests: knitr) and the vignette itself (%\VignetteEngine{knitr::knitr}). When Windows

I'm finalizing development of a package that will include a vignette. Without the vignette, the package builds fine with no warnings and is ready for distribution. Now, I am following the directions for developing vignettes "Sweave, Part II: Package Vignettes" by Friedrich Leisch. I am using a windows XP machine (other session info below). Here is what I have done. 1) I add the

Dear R-sig-debian, As of last night, we are running into a build failure when trying to compile the development version of R from the svn repository, Revision: 64090: ./configure && make -j4 distclean && ./configure && make -j4 [lots of normal compile output not shown...] building/updating vignettes for package 'utils' ... processing 'Sweave.Rnw' Error:

Dear R-Devel, Note: I posted a similar message to R-sig-debian yesterday because I assumed it was a Debian issue, received response that it it may be more appropriate for r-devel since it involves building from the svn version. As of Oct 21, we are running into a build failure when trying to compile the development version of R from the svn repository. The problem still persists as of

Hi, I am trying to create a Bioconductor package. Everything installs and checks fine. Now I'm on my last step, which is to create a vignette. I'm trying to test the Sweave process, to make sure I can build a vignette. I am stuck at the texi2dvi stage, which fails when I try to process the example Sweave-test-1.tex file. I am using Windows binary R distributions, and have the same

Thanks, Duncan. The files in question are Emacs Org-mode files, and I think these are more or less isomorphic to Rmd files, but I haven't used Org-mode in a long time, so I think the mapping (Org-mode ==> Rmd) would be painful. -- Mike On Mon, Feb 19, 2018 at 1:20 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 18/02/2018 9:06 PM, Michael Hannon wrote: >>

Hi, Recently I saw a couple of cases in which the package vignettes were somewhat complicated so that Stangle() (or knitr::purl() or other tangling functions) can fail to produce the exact R code that is executed by the weaving function Sweave() (or knitr::knit(), ...). For example, this is a valid document that can pass the weaving process but cannot generate a valid R script to be source()d:

Hi, I want to have a "vignette" in one of my R packages. Hence, I added an Sweave file into the /inst/doc subdirectory of this package. Unfortunately, 'R CMD check' gives a warning: ========================================== [...] * checking tests ... OK * checking package vignettes in 'inst/doc' ... WARNING --- f?hre texi2dvi auf Vignetten aus * creating

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