quarto-dev / quarto-dev/quarto
Chunk (cell) options in Quarto files should be treated differently from comments by the syntax parser in VS Code / Positron
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Bug description
Currently, chunk or cell options in Quarto (qmd) files are treated the same as comments. Hence, they often get low-visibility style:
Ideally, they should get its own treatment so that they could be assigned higher visibility without affecting actual comments.
System details:
Positron and OS details:
Positron Version: 2025.08.0 (user setup) build 130
Code - OSS Version: 1.102.0
Commit: 76ddce53e85437b013671fe7d91a3a1c54f48341
Date: 2025-08-01T20:29:20.753Z
Electron: 35.6.0
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Windows_NT x64 10.0.26100
Steps to reproduce
No response
Actual behavior
No response
Expected behavior
No response
Your environment
No response
Contributor guide
No contributing guide indexed for this repository
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 styling issue in a Quarto qmd file in VS Code or Positron, then trace the syntax parser behavior for chunk options and comments. Done means chunk options receive distinct, higher-visibility styling without changing the treatment of regular comments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100