quarto-dev / quarto-dev/quarto

Code chunks in fenced divs within VS Code's don't have a run cell button

Open
#99 1 comment 0 reactions 1 assignee View on GitHub

@jjallaire is already working on this.

Since Jan 3, 2023.

bug vscode
Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

Bug description

Code chunks within a .column fenced div do not allow for interactive use.

Quarto v1.2.269
VS Code v1.73.1
Quarto Ext v1.56.0
Mac + Python 3.10.6

Reprex Code - doesn't really matter though, even 1+1 works
---
title: "No Run code button in VS Code"
format: html
---

## Quarto, unified syntax

This syntax also applies across code-chunks

:::: {.columns}

::: {.column width="40%" .fragment}

```markdown
::: {layout-ncol=2}
![](image1.png)

![](image2.png)
:::
```

:::

::: {.column width="60%" .fragment}

```{python}
#| echo: fenced
#| eval: true
#| layout-ncol: 2

from plotnine import ggplot, geom_point, geom_boxplot, aes, stat_smooth, facet_wrap, theme
from plotnine.data import mtcars

# plot 1 in column 1
plot1 = (ggplot(mtcars, aes('wt', 'mpg', color='factor(gear)'))
   + geom_point() + stat_smooth(method='lm')
   + facet_wrap('~gear')).draw(show=True)

# plot 2 in column 2
plot2 = (ggplot(mtcars, aes('cyl', 'mpg', color='factor(cyl)'))
+ geom_boxplot()
 ).draw(show=True)
```

:::

::::

image

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.