similar to: customize building package vignettes

Hi all, I'm struggling a bit to get pgfSweave to lazyload objects when compiling a .Rnw file for a second time. Caching works fine except that for every run all objects get cached again and again. I've used cacheSweave which works fine; all cached objects from code-chunks with option cache = TRUE are lazy loaded. I've tried it on two machines ... I'm pretty sure I'm

Hello all, I would like to ask several questions regarding cacheSweave: 1) Is there a way to set "cache=true" globally? (I tried it using \SweaveOpts but it didn't seem to work) 2) Is there a way to "flush" specific cache once it is created? (other then erasing the entire cache directory)? Changing the code in the code chunk seems to do it, but I am not sure to what

Hi there I have a problem with using Sweave in combination with the option driver = cacheSweave. Whichever code I try to run - when it comes to converting the tex file into pdf it comes up with the same errors (\csname \endcsname errors). Does anybody have an idea what it going wrong? > Sweave("pgfSweave-example.Rnw",driver = cacheSweaveDriver) Writing to file

Hi, I released knitr 1.1 to CRAN a few days ago: http://cran.r-project.org/package=knitr See all new features and changes at https://github.com/yihui/knitr/blob/master/NEWS.md#changes-in-knitr-version-11 The version 1.0 does not imply perfect stability or maturity. The major version number was bumped from 0.x to 1.x due to a number of important features and the breaking of compatibility with

Hi, I released knitr 1.1 to CRAN a few days ago: http://cran.r-project.org/package=knitr See all new features and changes at https://github.com/yihui/knitr/blob/master/NEWS.md#changes-in-knitr-version-11 The version 1.0 does not imply perfect stability or maturity. The major version number was bumped from 0.x to 1.x due to a number of important features and the breaking of compatibility with

The knitr package version 0.5 is on CRAN now. It has gone through extensive development in the past few months, and about 200 issues were solved (https://github.com/yihui/knitr/issues) thanks to the feedback of users, which greatly improved the quality and usefulness of this package. For a complete list of changes, see https://github.com/yihui/knitr/blob/master/NEWS Most notable new features are:

The knitr package version 0.5 is on CRAN now. It has gone through extensive development in the past few months, and about 200 issues were solved (https://github.com/yihui/knitr/issues) thanks to the feedback of users, which greatly improved the quality and usefulness of this package. For a complete list of changes, see https://github.com/yihui/knitr/blob/master/NEWS Most notable new features are:

The knitr package was designed to be a transparent engine for dynamic report generation with R, solve some long-standing problems in Sweave, and combine features in other add-on packages into one package. It is a general-purpose package, and currently supports LaTeX, HTML and Markdown (still extensible). See the package website [1] to get started; see the package manuals ([2], [3] and [4]) for a

The knitr package was designed to be a transparent engine for dynamic report generation with R, solve some long-standing problems in Sweave, and combine features in other add-on packages into one package. It is a general-purpose package, and currently supports LaTeX, HTML and Markdown (still extensible). See the package website [1] to get started; see the package manuals ([2], [3] and [4]) for a

At long last pgfSweave has finally made its way to CRAN. The pgfSweave package is about speed and style of graphics. For speed, the package provides capabilities for ?caching? graphics generated with Sweave on top of the caching funcitonality of cacheSweave. For style the pgfSweave package facilitates the integration of R graphics with LaTeX reports through the tikzDevice package and eps2pgf

At long last pgfSweave has finally made its way to CRAN. The pgfSweave package is about speed and style of graphics. For speed, the package provides capabilities for ?caching? graphics generated with Sweave on top of the caching funcitonality of cacheSweave. For style the pgfSweave package facilitates the integration of R graphics with LaTeX reports through the tikzDevice package and eps2pgf

Dear list, I wish to use a specific driver to process an sweave document in the inst/doc directory of a package. Specifically, I would like to use either cacheSweave or pgfSweave to speed up the creation of the vignette which requires lengthy computations. The same request would also apply to the highlight driver, to provide syntax highlighting of R chunks. In "writing R extensions" I

Dear list, I wish to use a specific driver to process an sweave document in the inst/doc directory of a package. Specifically, I would like to use either cacheSweave or pgfSweave to speed up the creation of the vignette which requires lengthy computations. The same request would also apply to the highlight driver, to provide syntax highlighting of R chunks. In "writing R extensions" I

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 have a function knit_expand() and its source/Rd are below: https://github.com/yihui/knitr/blob/master/R/template.R#L43-L44 https://github.com/yihui/knitr/blob/master/man/knit_expand.Rd When I run R CMD check on the package I get this warning (with both R 2.15.2 and R-devel): * checking for code/documentation mismatches ... WARNING Codoc mismatches from documentation object

Will there be anything wrong if you do not set these options? Regards, Yihui -- https://yihui.name On Mon, Jun 12, 2017 at 2:24 AM, <G.Maubach at weinwolf.de> wrote: > Hi Yihui, > Hi Duncan, > > I corrected my typo. Unfortunately knitr did not find my plots in the > directory where they reside which is different from the Rmd document. > > The documentation of knitr

Dear Yihui, I have created a reproducible example at https://github.com/ThierryO/utf8vignette The \usepackage{} line is needed, otherwise R CMD check --as-cran will give a warning. %\VignetteEncoding{UTF-8} did not solve the problem. I use rmarkdown_0.3.11 HTML vignette is not an option as the vignette demonstrates the use of a custom beamer output format. Best regards, Thierry ir. Thierry

On 09/12/2014 11:13 AM, Yihui Xie wrote: > A few things to clarify: > > 1. You do not necessarily have to keep the \usepackage{} line if you > use %\VignetteEncoding{UTF-8}, because Pandoc will use UTF-8 anyway in > its LaTeX template. > > 2. Perhaps the vignette engine in R has done something clever to > convert utf8 to UTF-8, but I'd recommend

On 18/12/2014, 12:17 AM, Yihui Xie wrote: > For the record, I saw a change had been made in R-devel: > https://github.com/wch/r-source/commit/d53b098 (Thanks, Duncan) > Meanwhile, I also made a change in knitr to assume UTF-8 unless R > passes an encoding to the vignette engine: > https://github.com/yihui/knitr/commit/23c6c8e2 Both will solve the > original problem, but

For the record, I saw a change had been made in R-devel: https://github.com/wch/r-source/commit/d53b098 (Thanks, Duncan) Meanwhile, I also made a change in knitr to assume UTF-8 unless R passes an encoding to the vignette engine: https://github.com/yihui/knitr/commit/23c6c8e2 Both will solve the original problem, but apparently the former one is the ideal fix. Regards, Yihui -- Yihui Xie