posit-dev / posit-dev/positron

Quarto Outline shows commented-out headings

Open
#15,435 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: editor area: quarto bug support
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 11h
Merged PRs (30d)
206

Description

System details:

Positron and OS details:

Positron Version: 2026.08.0 build 331
Code - OSS Version: 1.124.0
Commit: a3a370d4187484ce962794408c76dab702978eaf
Date: 2026-08-05T17:02:37-07:00
Electron: 42.2.0
Chromium: 148.0.7778.97
Node.js: 24.15.0
V8: 14.8.178.14-electron.0
OS: Linux x64 7.1.4-204.fc44.x86_64

Describe the issue:

Headings that have been commented out (with a multi-line <!-- -->) are shown in the Positron Outline.

Steps to reproduce the issue:

  1. Open the following .qmd file:
---
title: "Untitled"
format: html
---

# Heading 1

<!-- TBD.

# Heading 2

TBD. -->

# Heading 3

TBD.
  1. See Outline:
Image

(Note that if the comment starts in the heading (<!-- # Heading 2), then the latter is correctly omitted from the outline.)

Expected or desired behavior:

Such headings should be omitted from the Positron Outline. That's the case in RStudio.


Many thanks in advance!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by opening the reported .qmd example in Positron and inspecting the Outline. The work is done when the heading inside the multiline comment is omitted while Heading 1 and Heading 3 remain visible, matching the expected behavior described in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.