quarto-dev / quarto-dev/quarto-cli
Indented code cells in enumerated lists render with fenced div indicators that shouldn't be visible on the output
Open
@mine-cetinkaya-rundel is already working on this.
Since Nov 13, 2023.
documentation
lint
pandoc
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
Including computational plot or table output in enumerated lists requires the code to be indented in the source in order to benefit from automatic numbering. However this results in fenced divs indicators appearing in the output when they shouldn't. See screenshot below.
Steps to reproduce
---
format: html
---
1. Item 1 text.
```{r}
plot(cars)
```
1. Item 2 text.
```{r}
cars |> head() |> knitr::kable()
```
Expected behavior
Did not expect ::: {.cell} and ::: {.cell-output-display} to be on the output.
Actual behavior
No response
Your environment
- IDE: Version 2023.12.0-daily+278 (2023.12.0-daily+278)
- R: R version 4.3.1
- Mac OS: Ventura 13.5
Quarto check output
Quarto 1.4.489
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.1.8: OK
Dart Sass version 1.55.0: OK
Deno version 1.33.4: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.4.489
Path: /Applications/quarto/bin
[✓] Checking tools....................OK
TinyTeX: v2023.08
Chromium: (not installed)
[✓] Checking LaTeX....................OK
Using: TinyTex
Path: /Users/mine/Library/TinyTeX/bin/universal-darwin
Version: 2023
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.9.6
Path: /Library/Developer/CommandLineTools/usr/bin/python3
Jupyter: 5.3.0
Kernels: python3
[✓] Checking Jupyter engine render....OK
[✓] Checking R installation...........OK
Version: 4.3.1
Path: /Library/Frameworks/R.framework/Resources
LibPaths:
- /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/library
knitr: 1.45
rmarkdown: 2.25
[✓] Checking Knitr engine render......OK
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.