similar to: Fortran issues. Was CRAN packages maintained by you

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

I'd say it is an expert-only option. If you do not understand what it means, I strongly recommend you not to set it. Similarly, you set the root_dir option and I don't know why you did it, but it is a typo anyway (should be root.dir). Regards, Yihui -- https://yihui.name On Fri, Jun 9, 2017 at 4:50 AM, <G.Maubach at gmx.de> wrote: > Hi Yi, > > many thanks for your reply.

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

Hola: Ya se ha comentado aquí algo sobre knitr, creo que la alternativa a Sweave (al que le tengo un gran cariño). La cosa va muy bien y lejos, os comento muy breve y os adjunto dos ficheros para muestra. Estoy buscando una forma de escribir potente y ágil para que los alumnos trabaje al cien por cien sin necesidad de aprender LaTeX (aqltugc). Para eso había encontrado markdown pero ¿cómo hacer

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 says: base.dir: (NULL) an absolute directory under which the plots are generate root.dir: (NULL) the root directory when evaluating code chunks; if NULL, the directory of the input document will be used

That is more or less what I had been doing for a long time (having both NEWS.md and NEWS), but decided not to do it any more last year. In fact, you can easily convert NEWS.md to a NEWS file that R's news() can understand, e.g. https://github.com/yihui/knitr/blob/947ad5fc94/Makefile#L8-L10 (if your NEWS.md is like this https://raw.githubusercontent.com/yihui/knitr/947ad5fc94/NEWS.md) I

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 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

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

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

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

Hi, I mentioned this at useR! 2012 but I guess the relevant R core members were not there (presumably Fritz, Duncan and Brian), so I'm making this wishlist again: Currently package vignettes have to be processed through Sweave, which is too restrictive since several add-on packages aiming to improve or extend Sweave have appeared (e.g. cacheSweave, pgfSweave, R.rsp, highlight, knitr, ...).

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:

On 09/12/2014, 4:38 PM, ONKELINX, Thierry wrote: > 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've just taken a look at the sources, and that's only in R-devel, it never

Dear R developers, I asked this question in r-help list but have not got a definite solution yet, and I think it might be more appropriate to ask developers or CRAN maintainers directly. Many software packages often have a menu item like "Check for updates" under the "Help" menu, e.g. Filezilla and Firefox, and I believe it is also necessary for R (at least for R GUI under