-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
work with pandoc package #178
Comments
Yeah, we could do that. I guess if there is no It does make the build process somewhat unpredictable, though, but I guess for most people it does not really matter what version of pandoc they are using. @cderv Which one of these is RStudio using by default, e.g. via the "Knit" button when editing the Rmd. Is it using the "system" version (if any), or the "rstudio" version? |
It depends - rmarkdown will use the latest Pandoc found by looking at
and it will use the latest version of pandoc found between the two. Unless RStudio IDE bundles Pandoc, now through its bundled Quarto. It will set this version to
pandoc package aims at simplifying testing and checking R code with different Pandoc versions. For this, it will work by default with its interally managed Pandoc version that can be installed with The pandoc package can be used though to retrieve information on other Pandoc version
Hope this clarifies and help
What is the pkgbuild relationship with Pandoc ? Is it for vignette building outside of RStudio IDE (when pandoc package has some helper to activate a version to work with
Maybe they can be useful with pkgbuild too - unless new background process though... |
The
pandoc
package provides a simple way of managing pandoc installs in R. It would be neat ifpkgbuild
could detect if thepandoc
package is installed and use it to get the pandoc path, rather than requiring users to set environment variables or add pandoc to the path.The text was updated successfully, but these errors were encountered: