quarto-dev / quarto-dev/quarto-cli
Long code block inside callout not rendered properly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
Running the quarto render on a project folder with a .qmd file that includes a long code block inside a callout block, generates a odd-formatted pdf file, as the one in attachment
test.pdf
Here a sample .md (.qmd) that causes this issue
test.md
The YAML of the project is the following
project:
title: "qproject"
output-dir: output
format:
pdf:
toc: true
toc-depth: 2
number-sections: true
code-line-numbers: true
code-block-bg: "#f0f3f5"
cap-location: top
I'm running quarto 1.2.335
> quarto --version
1.2.335
on vscode 1.77.3
> code --version
1.77.3
704ed70d4fd1c6bd6342c436f1ede30d1cff4710
x64
on Ubuntu 22.04 LTS
> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
quarto check returns the following
> quarto check
[✓] Checking Quarto installation......OK
Version: 1.2.335
Path: /opt/quarto/bin
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.9.16 (Conda)
Path: /home/edoardo/miniconda3/envs/DABDPA/bin/python
Jupyter: 5.3.0
Kernels: python3, bash
[✓] Checking Jupyter engine render....OK
[✓] Checking R installation...........(None)
Unable to locate an installed version of R.
Install R from https://cloud.r-project.org/
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.
- Please provide the output of
quarto checkso we know which version of quarto and its dependencies you're running.
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.
Research direction
Start by downloading test.md and the attached test.pdf, then reproduce the result with the provided project YAML using quarto render. Compare the generated PDF with the attachment and inspect the rendering path for long code blocks inside callouts. Done means the sample renders with the expected code-block formatting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- cli, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100