similar to: rmarkdown and font size

Hi Dan, Hi All, I read the below post. I am wondering how do I know which "keys" are available, e.g. "core.r" and "pre". Where kind I find the definition of what can be adjusted and which "words" to use? Kind regards Georg > Gesendet: Donnerstag, 08. Juni 2017 um 16:16 Uhr > Von: "Nordlund, Dan (DSHS/RDA)" <NordlDJ at

Buenas a todos. No me queda del todo claro si éste es el foro en el que preguntar o debería ser otro, ya que incluye cosas que van más allá de R. Sepan disculpar si me estoy excediendo. Estoy trabajando con RStudio y quiero generar un documento de salida en PDF; en ese documento tengo bastantes tablas anchas que no entran usando knitr::kable(la.tabla.ancha) Sí salen perfectamente en HTML

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

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

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

Hello, Thank you for the questions as well as remaining me of the default parameters in the yaml session. Indeed this seems to be the solution. But how would I assign package data as a default parameter? So originally I thought to render the markdown with : <code> data(sample_analysis) data(skylineconfig) x <- rmarkdown::render("report.Rmd", output_format =

Dear Duncan, Following your advice (Thank you for it) I did include into the vignettes params: configuration: !r get(data(sample_analysis)) data: !r get(data(skylineconfig)) And everything seemed (see below) to work fine. devtools::build_vignettes() builds the vignettes. Runs with NO error. By this the .Rmd file, html file and corresponding .R files is being placed into the inst/doc

Dear Duncan, Was close to giving up to use the parameterized rmarkown as vignettes. But your suggestions to use quote and eval, as well as to use the package parameter in data made it work, with all devtools::install,check,build and build_vignettes as well as with R CMD ... etc. But most importantly it also still works with: rmarkdown::render("vignettes/tr_srm_summary.Rmd",

So far you haven't provided a reproducible example yet. I wonder what exactly the object `sample_analysis` is. Sounds like it is an environment. If that is the case, devtools::build_vignettes() will tangle (for the meaning of "tangle", see ?tools::buildVignette) your vignette into an invalid R script. Environments cannot be represented via dput(), so knitr's purl() (eventually

Dear Community, I have an Rmarkdown vignette with optional child documents. Since all markdown files in the vingette folder are build when executing R CMD build I did place the child documents in /inst/ParametrizedReportChid/ so they are excluded from the build. I do reference them from the markdown file in the vignette folder by: ```{r referencingChildDocument} child_docs <-

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. Neither work for me. Not working for me either right now for some reason

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

That is strange. Another function in the same package (INBOmd::inbo_rapport) uses the same trick. I actually started by copying the post_processor() from that function. INBOmd::inbo_rapport() works both with and without BibTex. Working examples are source/inbo_rapport and source/inbo_rapport_basic from https://github.com/inbo/inbomd_examples. Note that you need some extra work after installing

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.

Buenas noches, Escribo este mail porque tengo un problema con rmarkdown, estoy creando un informe y me iba bien al generarlo como pdf, de repente me sale el siguiente error y no sé como solucionarlo: pandoc.exe: Error producing PDF from TeX sourceError: pandoc document conversion failed with error 43Además: Warning message:comando ejecutado '"C:/Program

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.

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

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,

Are you sure that you want to read in the output_file in text <- readLines(output_file, warn = FALSE)? best regards, Heinz Thierry Onkelinx wrote/hat geschrieben on/am 06.09.2017 11:41: > 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

I am trying to get rmarkdown with bookdown to include a table of contents in html output, and having trouble. Here is an example that I think illustrates the trouble. I have a file "test.Rmd" as follows: [127]% cat test.Rmd --- title: Test Document output: html_document: toc: true --- # Introduction some text # A section some more text [128]% If I run: library(rmarkdown)