Compiled versions of knitr and jupyter qmd files in a project #7482
Unanswered
royfrancis
asked this question in
Q&A
Replies: 1 comment 3 replies
-
I believe this to be related to your previous question: #7227 Something I do not understand, you set the output directory to "docs" but want the outputs to be in "compiled". Why not set the correct output? See: As it seems to be part of a bigger project (website), why not leveraging the pre-render script to render and move files before rendering the project itself? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
I have a mix of R qmd files (knitr) and python qmd files (jupyter). meta shortcodes are used. I would like to evaluate the meta shortcodes and create "compiled" versions of qmd. The knitr qmds will remain as qmd, but the jupyter qmd needs to be converted to .ipynb.
Here is a dummy project:
_quarto.yml
_metadata.yml
knitr.qmd
jupyter.qmd
I would like the compiled files in the "compiled" folder.
Here is what I have tried;
For knitr.qmd, something like this
quarto render knitr.qmd --to markdown-header_attributes --metadata engine:markdown
creates the compiled qmd into the docs folder. The
--output
argument doesn't help to change the output path.For python.qmd, I need to run the same thing
quarto render python.qmd --to markdown-header_attributes --metadata engine:markdown
and then
quarto convert docs/python.md --output compiled/python.ipynb
The
--output
actually works in this case.This seems quite chaotic. What is the best way to do this?
Additionally, the compiled output yaml contains a long list of all meta variables. Is it possible to keep only the variables in the original qmd file? In this example, only
title
andengine
.Beta Was this translation helpful? Give feedback.
All reactions