Hashes in code blocks interpreted as titles in ToC

jaalsa · April 21, 2025, 8:04pm

For example, this kind of md, which is a fenced code block (/code, ``` ``) with a common sh comment in it (“#”):

# This is a comment in a BSD configuration file:
resolvconf=NO

Gets interpreted as a level 1 tile in the ToC:

For context, both “Networking” and “Firewall” are legit lvl1 titles.

May I be misusing the code block syntax perhaps? Code blocks made with 4 spaces (not fencing) don’t cause that issue in the ToC.

Thanks!

zef · April 22, 2025, 11:54am

No, you’re doing it right. I just “simplified” the implementation of the TOC in v2, and it no longer takes into account fenced code blocks. So this is a bug. Could you create a github issue for this?

jaalsa · April 23, 2025, 6:13am

Sure, done

jaalsa · April 24, 2025, 10:28am

github.com/silverbulletmd/silverbullet

Hashes in code blocks interpreted as titles in ToC

opened 08:33PM - 22 Apr 25 UTC

chuskywalker

https://community.silverbullet.md/t/hashes-in-code-blocks-interpreted-as-titles-…in-toc/2215 For example, this kind of md, which is a fenced code block (/code, ``` ``) with a common sh comment in it (“#”): ``` # This is a comment in a BSD configuration file: resolvconf=NO ``` Gets interpreted as a level 1 tile in the ToC: ![Image](https://github.com/user-attachments/assets/d6f96b9f-b5d0-4567-b947-011616ae32d0) For context, both “Networking” and “Firewall” are legit lvl1 titles. Code blocks made with 4 spaces (not fencing) don’t cause that issue in the ToC. Comment from Zef Hemel: "...I just “simplified” the implementation of the TOC in v2, and it no longer takes into account fenced code blocks. So this is a bug. Could you create a github issue for this?"