# Is there a way to get "headings" in comments to show up in VSCode outline?

**URL:** https://discourse.julialang.org/t/is-there-a-way-to-get-headings-in-comments-to-show-up-in-vscode-outline/122460
**Category:** VS Code
**Created:** [November 10, 2024, 8:05am UTC](https://discourse.julialang.org/t/is-there-a-way-to-get-headings-in-comments-to-show-up-in-vscode-outline/122460 "2024-11-10T08:05:59Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![marius311](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marius311/32/3953_2.png) [@marius311](https://discourse.julialang.org/u/marius311)
#### Post date: [November 10, 2024, 8:05am UTC](https://discourse.julialang.org/t/is-there-a-way-to-get-headings-in-comments-to-show-up-in-vscode-outline/122460/1 "2024-11-10T08:05:59Z")

</div>

This isn’t Julia-specific per-se but Julia’s VSCode plugin certainly makes this use-case much more common so it seems like asking here might give the best chance of finding someone who could have an idea.

Anyway, I’m using julia-vscode’s inline evaluation instead of notebooks alot, but one thing I miss from notebooks is being able to make an outline to easily skip around large files. In notebooks you do this with markdown headers inside cells.

Is there any way to do this in Julia files that get used “as a notebook” with cell delimeters? Basically I want a file like the example shown below to to have the headings show up in the outline.

 ![image](https://global.discourse-cdn.com/julialang/original/3X/8/5/8502c5db20acac9b49bf09a4bf03fd8a36d53eae.png)

Of course this is kind of generic beyond Julia, but haven’t been able to find any VSCode options or settings that might allow this. Any suggestions? Thanks.

---

<div class="post-metadata">

### Author: ![artemsolod](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/artemsolod/32/20704_2.png) [@artemsolod](https://discourse.julialang.org/u/artemsolod)
#### Post date: [November 10, 2024, 9:38am UTC](https://discourse.julialang.org/t/is-there-a-way-to-get-headings-in-comments-to-show-up-in-vscode-outline/122460/2 "2024-11-10T09:38:13Z")

</div>

There is an issue about this since 2022, maybe if more people expressed interest it might bring more attention to this feature

> <https://github.com/julia-vscode/julia-vscode/issues/2894>
>
> Is it possible to display some sort of section information in Outline pane? I've… tried using cell syntax but it seems to be treated just like a comment and ignored. Can support for this be added within \`julia-vscode\` or is it upstream territory? Or may be there is syntax to make some sort of anchors in outline? Thanks!
> 
> !\[image\](https://user-images.githubusercontent.com/1939268/169646765-51f0338e-2518-4dba-a192-141f1836548d.png)

---

<div class="post-metadata">

### Author: ![caleb-allen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/caleb-allen/32/14054_2.png) [@caleb-allen](https://discourse.julialang.org/u/caleb-allen)
#### Post date: [November 11, 2024, 10:42am UTC](https://discourse.julialang.org/t/is-there-a-way-to-get-headings-in-comments-to-show-up-in-vscode-outline/122460/3 "2024-11-11T10:42:31Z")

</div>

I recently started using MARK comments to show headers on the mini map, but I don’t recall if they show on the outline (on mobile at the moment). Worth checking?

> <https://github.com/microsoft/vscode/pull/190759>
>
> This addresses #74843. It adds section headers to the minimap, sourced from regi…on markers and \`MARK:\` comments:
> 
> !\[vscode-minimap\](https://github.com/microsoft/vscode/assets/352830/96ccb921-1a35-4b20-b84f-e57d7124bd48)
> 
> \`MARK:\` comments behave the same way as they do in Xcode's minimap—if the comment contains a hyphen before the header text then it displays a horizontal separator line above the section header.
> 
> This PR adds three settings to control the appearance of the section headers, or to turn them off:
> 
> !\[vscode-section-header-settings\](https://github.com/microsoft/vscode/assets/352830/f2ff9c31-3e6e-4d50-884f-e8edc2b27c7a)
> 
> Feedback, testing and code fixes are very welcome!
