similar to: vignette/knitr help

Dear Mick, Note that both knitr and rmarkdown are listed under Suggests: both are required to compile the vignette. Installing rmarkdown should solve the problem. If not, please provide more information. OS, R version, digest version, ... Best regards, ir. Thierry Onkelinx Instituut voor natuur- en bosonderzoek / Research Institute for Nature and Forest team Biometrie & Kwaliteitszorg / team

On 5/3/16 11:29 AM, Thierry Onkelinx wrote: > Dear Mick, > > Note that both knitr and rmarkdown are listed under Suggests: both are > required to compile the vignette. Installing rmarkdown should solve > the problem. If not, please provide more information. OS, R version, > digest version, ... > > This is occurring in the context of an automated testing environment that

Buenas tardes, Al tratar de hacer en rstudio documentos pdf, word o html con un archivo rmd me sale un mensaje tal que así: "Rendering R Markdown documents requires updated versions of the following packages: knitr, rmarkdown. Do you want to install these packages now?" He probado a reinstalar esos paquetes (que ya tenía instalados) pero cuando vuelvo a aplicar knit to pdf,

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

Hi All, I have to compile a report for the management and decided to use RMarkdown and knitr. I compiled all needed plots (using separate R scripts) before compiling the report, thus all plots reside in my graphics directory. The RMarkdown report needs to access these files. I have defined ```{r setup, include = FALSE} knitr::opts_knit$set( echo = FALSE, xtable.type = "html",

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

Muchas gracias Carlos. Tengo las mismas versiones pero no logro separar los chunks cuando uso #+, pero si lo logro cuando uso #". Mi script es spin("prueba.R", knit = FALSE) y si me hace un Rmd. #+ a = c(1,2,3) #+ mean(a) Ejecuto, > spin("prueba.R", knit = FALSE) y obtengo un prueba.Rmd ```{r } a = c(1,2,3) ```{r } mean(a) ``` Pero si escribo: #' a =

Muchas gracias Carlos. Tengo la versión de knitr 1.14 Corrí el ejemplo que me dices y resulta en lo mismo, no se crean chunks diferentes. Parece que para separar chunks se debe incluir #' Por ejemplo, estas 2 líneas de códigos del ejemplo: #+ test-chisq5 sum(x^2) # chi-square distribution with df 5 #+ test-chisq4 sum((x - mean(x))^2) # df is 4 now Dan como resultado en el Rmd (todo queda

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

Dear all, I'm trying to use a Markdown vignette with UTF-8 encoding. It compiles well when knitting the vignette in RStudio, but it fails to recognize the UTF-8 settings when building the source package. Can someone point out what I'm doing wrong? I tried to put the relevant information below. Best regards, Thierry Details: Using 64-bit R 3.1.2 with encoding = "native.enc"

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

Hello, This is a problem I posted about already some time ago: https://stat.ethz.ch/pipermail/r-devel/2018-September/076786.html Finally, I did had some time to create a minimal package to reproduce the problem that vignettes with child can not be build. https://github.com/wolski/RmarkdownVignetteProblem The problem basically is that while all the vignettes can be build by running

Dear Duncan, The UTF-8 characters aren't properly rendered in the pdf version of the vignette. $?? ????? ?????? ?????? ????? ?? ?? is rendered as $????? ?????????? ???????????? ????? ?????? ? ???????? ???????? The same problem occurs when I use render("vignette.md", output_format = "mypackage::mystyle"), instead of render("vignette.md", output_format =

On 09/07/2018 3:24 PM, Witold E Wolski wrote: > Dear Yihui, > > Thank you for the valuable questions. > > sample_analysis is a "tibble" while > configuration is an "R6" class. > But I also have parametrized reports where I pass R reference classes > as arguments. > > This is the Rmd yaml params part corresponding to the error message. > >

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

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 %\VignetteEncoding{UTF-8} instead of %\VignetteEncoding{utf8} to make sure it is a valid encoding name,

Dear all, I'm trying to write a post_processor() for a custom rmarkdown format. The goal of the post_processor() is to modify the latex file before it is compiled. For some reason the post_processor() is not run. The post_processor() does work when I run it manually on the tex file. Any suggestions on what I'm doing wrong? Below is the relevant snippet of the code. The full code is

Suppose I have a file (named "tmp.rmd") containing: --- title: Test --- ```{r example, echo=FALSE, results='asis'} tmp <- data.frame(a=1:5, b=letters[1:5]) print( knitr::kable(tmp, row.names=FALSE)) ``` And I render it with: rmarkdown::render('tmp.rmd', output_format=c('html_document','pdf_document')) I get two files: tmp.pdf tmp.html Is

Dear Duncan, Thanks for chiming in. Could you explain how you set debug() on post_processor()? I've tried adding debug(post_processor) to rsos_article() or adding debug(post_processor) when after post_processor was defined in the debugger. Neither work for me. All supporting files are available within the package. The code below should be reproducible on your machine.

On 07/09/2017 2:04 PM, Duncan Murdoch wrote: > On 07/09/2017 10:11 AM, Thierry Onkelinx wrote: >> Dear Duncan, >> >> Thanks for chiming in. Could you explain how you set debug() on >> post_processor()? I've tried adding debug(post_processor) to >> rsos_article() or adding debug(post_processor) when after post_processor >> was defined in the debugger.