Suddenly ignoring some frontmatter

[cscherrer]

Hi, I'm giving a talk tomorrow, and I've been preparing it using Quarto. This is my first time using it, and I've been really enjoying it so far. I'm using Quarto from within VS Code, to produce a RevealJS presentation that uses Julia (so it's going through .ipynb).

This morning, the rendered output is suddenly different, and I have no idea why. The frontmatter and CLI call haven't changed. The .scss file still exists, and hasn't changed.

My frontmatter is

---
title: "Applied Measure Theory for Composable Statistical Modeling"
author: Chad Scherrer
execute:
    keep-ipynb: true
    keep-md: true
    echo: true
    daemon: 3000
engine: jupyter
format: 
    revealjs:
        logo: logo.png
        slide-number: true
        theme: [default, slides.scss]
        code-fold: false
        code-line-numbers: false
---

The (automated) CLI call is

quarto preview topos-talk.qmd --to html --no-browser --no-watch-inputs

Previously it was (correctly) producing a RevealJS presentation. Now it produces much more generic HTML, just very basic scrollable stuff. Searching that HTML for "reveal" gives no results.

As I said above, my presentation is tomorrow. I know this is short notice, but Quarto has been working great for the last week, until just this morning. I'd greatly appreciate if someone could please help me out with this.

Thank you!

[mcanouil]

With the command quarto preview topos-talk.qmd --to html --no-browser --no-watch-inputs you explicitly ask for the format to be htmlnot revealjs, thus you get an HTML following the default format.
Try:

quarto preview topos-talk.qmd --to revealjs --no-browser --no-watch-inputs

Or let Quarto do its thing by using your default and only format from the yaml.

quarto preview topos-talk.qmd --no-browser --no-watch-inputs

[cscherrer]

That makes sense, I'll try this. But why would the VS Code hotkey suddenly change? (I don't have a way to check the previous CLI calls)

[mcanouil]

VSCode default button will use quarto preview topos-talk.qmd --no-browser --no-watch-inputs.
But you have access to the main default format, i.e., --to html, --to pdf, and , --to docx.

PS: if the answer provided above actually solves your issue/question, please select it as the answer to let others know it has been answered.

[cscherrer]

From some experimentation, it seems that calling Render HTML redefines the shortcut. So on subsequent renders, it continues to render HTML. To get back to the YAML-specified settings, you need to call Render from VS Code, which will then reset the shortcut back to normal.

Or maybe a clearer way to put it... The shortcut doesn't call Render, but instead calls the render command called most recently.

This seems like a bug to me, or at least something that could be made more clear in the docs.

In the context of VS Code, I think this is the solution - call Render from the ctrl-shift-P options to reset the shortcut. I'll mark it as the solution. Thanks for the quick response!

[mcanouil]

From the button, you can do that, no need to get to the command palette.

Screen.Recording.2022-08-31.at.16.44.18.mov

[cscherrer]

One thing that was throwing me is that RevealJS is HTML, so I wouldn't expect --to html to be a problem.

[mcanouil]

--to does not define the type of document to be rendered but the format, although "render Word" feels inconsistent with the other options since "Word" is a software, while the format is docx.

[cscherrer]

Right, I see that now. Just pointing out that this is a subtle point and, at least for me, a source of confusion.

[mcanouil]

I made a PR to the VSCode extension for make the buttons name consistent, i.e., focussing on formats/extension which could alleviate a bit the possible confusion.