⌘ + ↵ only sends current line to console in .qmd chunks

[abichat]

Bug description

After updating to Positron 2025.07.0 (build 204) this morning, I can no longer execute multi-line R chunks in .qmd documents with ⌘ + ↵ on macOS.
The issue occurs only when the closing back-ticks of a code chunk (```) are immediately followed by a callout start (:::) with no blank line in between. In that situation, regardless of the cursor position, only the line where the cursor sits is sent to the console, so the code that reaches the console is incomplete or incorrect.

It worked well (with and without the blank line) with my previous Positron version (Positron-2025.04.0-250).
The problem affects manual execution only, the preview rendering is unaffected.

Steps to reproduce

---
title: "Test"
output: html
---

```{r}
library(dplyr)

iris %>%
  group_by(Species) %>% 
  summarise(mean = mean(Sepal.Width))
```

::: {.callout-caution}

```{r}
sessionInfo()
```
:::

However, inserting a blank line between the closing ``` of the code chunk and the closing ::: of the callout restores the expected behaviour.

Your environment

Positron

Positron Version: 2025.07.0 build 204
Code - OSS Version: 1.100.3
Commit: 03ae7a5393c776bb24c23d2aa6a6bfbba90cbc5e
Date: 2025-06-30T16:29:03.492Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Quarto

quarto -v 1.7.29

Identifier
quarto.quarto
Version
1.123.0
Last Updated
2025-06-18, 09:07:52

[juliasilge]

You do need that whitespace, I believe. We are noticing that folks may not be aware of the fact that pandoc markdown requires these kinds of empty lines, as specified here:

https://pandoc.org/MANUAL.html

Note:

Like regular code blocks, fenced code blocks must be separated from surrounding text by blank lines.

We have quarto-dev/quarto-cli#12255 logged to improve the documentation around this and plan to improve our parsing of markdown. In the meantime, as a workaround, if you see problems like this, check your whitespace usage.

Thank you for this report! 🙌

[cderv]

I am curious which change enforces these rules for the interactive execution?

The document renders fine in the current state, so this is indeed tricky to understand for users.

Pandoc does not seem to be bothered by those blank lines always

❯ pandoc -f markdown -t native
```{.r}
library(dplyr)

iris %>%
  group_by(Species) %>% 
  summarise(mean = mean(Sepal.Width))
```

::: {.callout-caution}
```{.r}
sessionInfo()
```
:::
^Z
[ CodeBlock
    ( "" , [ "r" ] , [] )
    "library(dplyr)\n\niris %>%\n  group_by(Species) %>% \n  summarise(mean = mean(Sepal.Width))"
, Div
    ( "" , [ "callout-caution" ] , [] )
    [ CodeBlock ( "" , [ "r" ] , [] ) "sessionInfo()" ]
]

It correctly parses a CodeBlock inside a Div, so I was unsure which was really causing the inline interactive running to fail.

Cell is correctly detected and "Run cell" is applied. Only in cell interactive execution fails because of a missing blank line somewhere later in the document.

Hopefully Carlos work on parsing Markdown in a better way will help with all this.