quarto-dev / quarto-dev/quarto-cli
quarto-1.4.80-macos unable to recognize the content of the "block" in div when compiling beamer.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
A very frustrating problem, which did not exist in my previous version.
I want to input the Block block in beamer as follows in QMD:
:: {.block}
content
:::
So that it can be displayed as a block in be after compilation. This was successfully done in previous versions, but cannot be achieved in the latest(quarto-1.4.80-macos). After compilation, only content is displayed instead of the block.
Has this feature been removed from new version or is it just a bug?
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 provide the output of
quarto checkso we know which version of quarto and its dependencies you're running. - Please document the operating system you're running. If on Linux, please provide the specific distribution.
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 reproducing the supplied .qmd block example with quarto-1.4.80-macos while compiling a beamer document, then compare the generated output with the previous version described in the report. Done means the {.block} div is rendered as a beamer block rather than leaving only its content; the issue does not name a source file or test to inspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, markdown
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100