5 ms·
I wish there was a better way to run quarto as a script, as in, as fast as `source` in R and `include` in Julia. Current behavior 1. Has scoping rules that mak
by pdeffebach 3y ago
I wish there was a better way to run quarto as a script, as in, as fast as `source` in R and `include` in Julia. Current behavior
1. Has scoping rules that make it difficult to debug
2. Has low latency, making it frustrating for debugging.
- cscheid 3y agoThanks for the feedback. The scoping rules are by design and match .ipynb workflows in the case of multiple documents, so we're unlikely to change it. The render latency of quarto is definitely higher than we'd love, but we have a plan and have been steadily improving it. Quarto 1.4 is generally about 20% faster than 1.3, and we have performance regression infrastructure to not let us slip on it.
- pdeffebach 3y agoThanks for the feedback! Just to re-state my case in clearer terms: For my personal workflow (others may differ), compiling to html is only done once at the end of a session, and the latency wouldn't matter if it could execute like a script. Weave.jl^[1] has a great feature called `include_weave` which has the features I like. But take my feedback with a grain of salt. I generally just save things in folders and compile a pdf separately with many tables and figures. [1] https://weavejl.mpastell.com/stable/usage/#include_weave https://weavejl.mpastell.com/stable/usage/#include_weave
- cscheid 3y agoI think this is going to be right up your alley, then: https://quarto.org/docs/computations/render-scripts.html https://quarto.org/docs/computations/render-scripts.html
- pdeffebach 3y agoPerfect! So glad this exists!