Open
0 of 1 issue completed
Description
In our TypeScript codebase, we need a source of truth for which input files produce which output files (and which temporaries).
Potential wins once we have this:
- parallelization
- change output locations (including slugs, etc)
- safer parameterized reports
- avoid file overwriting
Issues:
- The
--outputtrigger overwrites previously rendered file #6472 - Quarto deletes the original
index.ipynbfile when rendering a different notebook (index.render.ipynb) withoutput-file: index, despite the original file being explicitly ignored in the project configuration. #10841 - Race condition when running multiple instances of quarto #6116
- Parallel Computing - using one .qmd to render n output files - cannot open the connection #5861
- Parallel creation of parameterized reports fails due to file conflicts #4730
- [VSCode] Rendering Deletes ipynb File #4802
- improvement: make
--outputoption generate directories which respect the option #690 -
quarto inspectand temporary directories #906 - Long render times #1152
- TeX file is not moved to output-dir #1294
- [Feature request] Can Quarto please create_all_ temporary files _not_ in the same directory with my source files? #1666
- Quarto should output websites with "pretty" URLs #2065
- communicate format output to all engines #2216
-
output-fileparameter follows file location, not project (_quarto.yml) location. #2375 - Render to a new file name stores resources in directory with name of qmd file #2363
- Getting file not found errror when setting
revealjssetting #6809 - Rename
texoutput tooutput-filewhenkeep-tex: true#6045 - output file name conflict when two formats targets same extension (like html and revealjs) #4583
- Quarto render / preview immediately reports "SyntaxError: Unexpected end of JSON input" #6392
- Multiple pdf format fail with generated figures #8367
- Supporting file are cleanup to soon when using multiformat #8373
Notes
Lockfiles
When fixing #6472, we should consider a design for lockfiles, so that different instances of running quarto (which happens often when running a VS code preview and a command-line render, like in our test suite) don't step on each other's toes.
-
.quarto directory should have quarto's version information in it to remove stale crossref index and prevent unexplicit errors #8626 (.quarto should be versioned)
Other things to do
- when doing notebook embedding, we currently do a lot of this kind of "file exists" reasoning. That should be a part of this planner instead.
- this is also involved in getting multiple versions of a same page to be rendered (dark + light, mobile + desktop, etc)