similar to: Compatibility with R 2.15.x: Makefile for (non-Sweave) vignettes in vignettes/?

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

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

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,

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

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 /

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

Greetings. The group that I work with has just started using the approach outlined in Karl Broman's handy primer: http://kbroman.org/pkg_primer/pages/vignettes.html to create vignettes for a couple of R packages. This works fine as long as we have a current Rmd version of the vignette. But we have some old PDF documents that we'd like to include as vignettes as well. I'd like

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

I apologize that these questions are stupid and literal. I write to ask for clarification of comments in the R extensions manual about vignettes. I'm not great at LaTeX, but I'm not a complete novice either, and some of the comments are puzzling to me. 1. I'm stumbling over this line: "Make sure all files needed to run the R code in the vignette (data sets, ...) are accessible

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

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

Hi, I found the following problem with recent R-devel (2010-08-26 r52817) on Windows (32-bit and 64-bit): 'R CMD build <pkg>' gets stalled during vignette creation for packages that have a Makefile in <pkg>/inst/doc. It seems that the problem is that the commands used in the Makefile for converting .tex to .pdf are not able to locate the Sweave.sty file anymore (if I drop

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:

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

I'm adding a couple of vignettes to an existing package. When I make a change to the sweave file, and run the check command, c:\conifers\trunk>R CMD check rconifers I get the following message(s) in the 00check.log file: * checking for unstated dependencies in vignettes ... OK * checking package vignettes in 'inst/doc' ... WARNING Package vignette(s) without corresponding PDF:

Hello, Sweave lets you use alternative drivers through the driver argument, and several packages take advantage of that and define custom Sweave driver for various purposes. Most of them are listed on the Reproducible Research CTV: (http://cran.r-project.org/web/views/ReproducibleResearch.html) The next natural step is for package developpers to take advantage of this in their vignettes. In

Hi, in Section 'Writing package vignettes' of 'Writing R Extensions' it says: "Whenever a Makefile is found, then R CMD build will try to run make after the Sweave runs, so PDF manuals can be created from arbitrary source formats (plain LaTeX files, ...). [...] Note that the make step is executed even if there are no files in Sweave format, [...]". In my package,

On 19/02/2018 5:47 AM, Michael Hannon wrote: > 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. If they aren't LaTeX then they won't be able to masquerade as Sweave files, so things are

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