SQL chucks appear different with R chunks when eval is false

[WilliamTylerBradley]

Bug description

I'm redoing my website using a Quarto blog. When I have post set to eval: false with a SQL code chunk and an R code chunk, it looks fine. When I remove the R part, it changes formatting.

To reproduce, I have a blog post with each of these options:

1. Blog post without R chunk.

---
title: "Test without R"
date: "2022-08-24"
execute: 
  eval: false
---

```{sql test}
SELECT * FROM EXAMPLE;
```

![Test without R code](https://user-images.githubusercontent.com/15098268/186791358-28b8b09a-77f0-4d36-948d-79c68c563e9c.png)


2) Same blog post, but with a blank R chunk at the end.
---
title: "Test with R"
date: "2022-08-25"
execute: 
  eval: false
---

```{sql test}
SELECT * FROM EXAMPLE;
```

```{r}
```

---

The SQL section outputs are different.

Screenshot of the first blog post. Formatting does not have syntax highlighting.

Screenshot of the second blog post. This does have highlighting.

Screenshot of the home page.

I don't know why they don't match. I just updated to the newest Quarto version (but I think it was happening on the previous one too). This is on RStudio 2022.07.1 Build 554. "Spotted Wakerobin" for macOS, on Monterey.

Checklist

• Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
• Please format your issue so it is easier for us to read the bug report.
• Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
• Please document the operating system you're running. If on Linux, please provide the specific distribution.

[cderv]

They don't match because I believe in the second example by adding an R chunk ```{r} you triggered the auto binding for computation engine to use R and knitr. In that case sql chunk is recognize and process by knitr. In the first example, I think it will use no engine by default (see about auto detection https://quarto.org/docs/computations/execution-options.html#engine-binding). sql engine in a computation chunk is not something Quarto knows how to deal by default. You need to specificy engine in this case.

If you add in YAML header

engine: knitr

in your first example, I think you would get the same in both case.

Not that if you only want highlighting of the code with no execution, you need to use syntax without the braces
https://quarto.org/docs/authoring/markdown-basics.html#source-code

[WilliamTylerBradley]

Ok, cool. Both those options worked for me. The auto binding also explains why I wasn't getting the same result when using python instead of R. Thanks!

[eitsupi]

I noticed that the VS Code extension has added the ability to detect the knitr engine and send the contents of Python code blocks to the R terminal.
quarto-dev/quarto@5b1e799

It would be great if some major code blocks, such as SQL, could support something similar. (Of course, given things like chunk options, it would be difficult to fully cover knitr's functionality)

[mcanouil]

You could ask for that in the vscode extension repository: https://github.com/quarto-dev/quarto

[eitsupi]

You could ask for that in the vscode extension repository: quarto-dev/quarto

Maybe quarto-dev/quarto#26