Christophe Dervieux

Both **rmarkdown** and **pandoc** (if `yaml_metadata_block` extension is not deactivated) will use yaml blocks to look for informations. Pandoc allows several YAML blocks in the document but currently **rmardown** only...

> Are there occasions when knitr, rmarkdown and the like use "their" definition of the metadata? Some of the metadata fields are used by **rmarkdown** and others to know what...

> Why not utilize Pandoc itself to parse the metadata because that's more robust? Pandoc sets the variable meta-json, so a template that just contains $meta-json$ could be used for...

About timing, I agree this is a concern. I did some more bench using bookdown book as example Bench on Rmd from bookdown book The function gained a normalized path...

Doing this change could be breaking, if any other package is looking into `pandoc_args` value of the output format. ``` r rmarkdown::html_document()$pandoc$args #> [1] "--embed-resources" #> [2] "--standalone" #> [3]...

Thanks for you feedback. This confirms my intuitions. I'll handle that with a new function in **pandoc** package (https://github.com/cderv/pandoc/issues/37) > believe we could also detect any change of Pandoc version...

Thanks for the reminder @lfmcmillan - I added an update

> Unfortunately, I am unable to create a reproducible example. Unfortunately without reproducible example, or at least a shared document or anything, it will be hard to help and look...

> Is there a way I can have a log of what was run behind the scene when I press preview? Does it run knit?! I don't know what RStudio...

> Do you have any suggestion on what to check/fix for this cache issue from RStudio? Unfortunately no. This could be a RStudio IDE related issue. Maybe you can try...