similar to: make file.rename return invisible

I need some help understanding a problem running the tests on the 'digest' package. Initially, I got the message that the 'knitr' package was needed to run vignettes: Running vignettes for package ?digest? Error in loadVignetteBuilder(vigns$pkgdir) : vignette builder 'knitr' not found So I installed the knitr package and all its dependents (?mime?, ?stringi?,

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

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

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 =

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"

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,

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

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

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,

Dear R-devs, Scenario: When checking a package via `R CMD check package_tar.ball`, required / suggested packages may be missing. R subsequently returns a list of packages that are missing (delimited by spaces). Example: ``` R CMD check glmSparseNet_0.99.13.tar.gz * using log directory '/home/ubuntu/Bioconductor/glmSparseNet.Rcheck' * using R Under development (unstable) (2018-06-06

Muchas gracias, Jos Antonio y Carlos. Estaba por escribir sandeces varias. Comento, por si hay algn lector, que como yo, se guarda los correos con respuestas a problemas posibles. No estaba usando|header.tex|, que es necesario para una como para otra solucin. El encabezado queda as: |---|| ||title: "Tablas que no entran"|| ||author: "Sandia Urlia"|| ||date: ""||

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 =

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

Buenas, he intentado varias veces instalar knitr y Rmarkdown tanto desde Rstudio como desde la terminal de Ubuntu usando diferentes codigos y en nunca consegui q lo instalara. el error q tira es el siguiente: Warning in install.packages : installation of package ?/tmp/RtmpavyTWw/downloaded_packages/stringr_1.0.0.tar.gz? had non-zero exit status Alguien me podria ayudar, porq estoy dejando

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

Look at the spin and stitch functions in the knitr package if you want to process an existing script into an output that mixes the code run with the output. Look at the txtStart and related functions in the TeachingDemos package if you want the code and output saved in a file from a session where you are typing in commands. If in general you want text, code, and output mixed, learn the knitr

Hola ¿Quizá por aquí? https://github.com/yihui/knitr/issues/268 El 13 de enero de 2017, 12:26, Rubén Gómez Antolí <lobo en mucharuina.com> escribió: > > > El 13/01/17 a las 11:50, Antonio Maurandi López escribió: > > Hola lista: > > > > Una duda rápida (espero). > > > > ¿Se puede hacer un "inlcude" o un "input" en markdown? >

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

On 06/09/2017 5:41 AM, Thierry Onkelinx wrote: > 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

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.