posit-dev / posit-dev/positron
Bug: Quarto appears twice in the Outline for repository files
@juliasilge is already working on this.
Since Aug 12, 2026.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
Summary
The Outline view displays the Quarto document section twice when a Quarto document is opened from a repository. Both entries contain the same heading hierarchy, resulting in a duplicated outline.
System details
<details> <summary>Positron and OS details</summary>
Component | Version / details -- | -- Positron | 2026.07.1 build 5 Code - OSS | 1.118.0 Commit | d3cdd608df5afa3378c24c9a9c81b01fe1433a87 Build date | 2026-07-08T19:52:09-06:00 Electron | 39.8.8 Chromium | 142.0.7444.265 Node.js | 22.22.1 V8 | 14.2.231.22-electron.0 OS | Darwin arm64 25.6.0 Quarto | 1.135.0</details>
<details> <summary>Session details</summary>
Document type: Quarto document (
.qmd)Code cell language: Python
LLM model: Not applicable
</details>
Steps to reproduce
Open a repository in Positron.
Open a Quarto document (
.qmd) containing at least two headings and a Python code cell.Open the Outline view.
Observe that the
Quartosection appears twice.Expand both sections and observe that they contain the same heading hierarchy.
Actual behavior
The Outline contains two identical Quarto sections, each with the same headings beneath it.
Duplicate Quarto sections in the Outline view
Expected behavior
The Outline should display the Quarto document only once, with a single Quarto section and one heading hierarchy beneath it.
Error messages
No error messages were observed in the UI, Output panel, or Developer Tools console.
Additional context
This may be related to Outline support for files opened from repositories. The duplicate section is distracting and makes the Outline harder to use for document navigation.
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.