Render with Assumed Non Changing Code

[RoyiAvital]

I use Quarto within VS Code.

I render the HTML output (Reveal.JS) using the Render button:

I can see that when I render over and over with short period in between the process is much faster as it assumes the code sections are not changed, hence skip the process of running the code.
Yet, when there is a longer period from my last render, even if no code is changed, it will rerun the code.

I was wondering if there is a command within VS Code or on the command line that can force render mode with assuming the current code hasn't changed form the last time the render has happened.

This will make thing much faster when working with Quarto.

[mcanouil]

The Quarto execute.freeze option is what you are looking for.

[RoyiAvital]

For some reason I remember the cache option being only available on Linux or so.
Anyhow, it would be great to have this feature working to make things easier when working on a document with a lot of code.

[cscheid]

For some reason I remember the cache option being only available on Linux or so.

Just to clarify, that's definitely not the case. If you could point us to where in the documentation you read that, I'd be happy to fix it.

[RoyiAvital]

@cscheid , I am not sure about this. The important thing is you clarify the current situation.

[cscheid]

It looks like your document isn't using the cache.

You need to enable caching like the documentation suggests:

execute:
  cache: true

There's a difference between:

• our execution daemon (which speeds up the starting of the jupyter process)
• our freeze option (which prevents the running of any engine, jupyter or otherwise)
• the cache option, which reuses results from particular cells, using the knitr or jupyter cache

In passing, I'd also ask that you make an additional effort to be kind to the developers as we respond here. When you write "The important thing is", your message implies that other things the devs do are not important. Everyone has a lot on their plate.

[RoyiAvital]

@cscheid , I meant the important thing is that, you, the knowledgeable confirmed the cache works on Windows (It seems I mixed it with the daemon you mentioned).

I am sorry if my choice of words was not clear.
I have nothing but respect to this project and those who keep pushing it forward.