Bug: Header Increment does not recognize setext-style headings
See original GitHub issueDescribe the Bug
The “Header Increment” rule does not seem to recognize setext-style headers as headers.
How to Reproduce
Steps to reproduce the behavior:
- Create an Obsidian document with headers as below
- Lint the file
- “Header 3” is incorrectly changed to an H1
Example to reproduce issue with
Header 1
========
Header 2
--------
### Header 3
Expected Behavior
Header 1
========
Header 2
--------
### Header 3
Actual Behavior
Header 1
========
Header 2
--------
# Header 3
Device
- Desktop
- Mobile
Issue Analytics
- State:
- Created a year ago
- Comments:8
Top Results From Across the Web
markdownlint/Rules.md at main - GitHub
Any rule whose heading is struck through is deprecated, but still provided for backward-compatibility. MD001 - Heading levels should only increment by one...
Read more >MS Word - Built in Headings not working - Microsoft Community
I am having a problem with my MS word, I am currently trying to format one of my reports for varsity so that...
Read more >doc/Rules.md · Gitee 极速下载/markdownlint - Gitee.com
MD001 - Heading levels should only increment by one level at a time ... scenario because the unordered sublist is not recognized as...
Read more >markdown的语法-英文_剑之所向的博客
MD001 - Heading levels should only increment by one level at a time ... the unordered sublist is not recognized as such by...
Read more >Markdown Syntax Documentation - Daring Fireball
Markdown supports two styles of headers, Setext and atx. Setext-style headers are “underlined” using equal signs (for first-level headers) and dashes (for ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah it is something that would need to be added. Since this is something that needs to be addressed in all heading rules and not just this one rule, I am going to get to it once I get through the current list of features to work on. I will put it at the bottom of the queue for things to work on above the backlog content.
Hm. That’s a really good question. I think a setting in the Rule of whether to use setext or atx headers is the answer. Either way it should recognize setext headers, but unless that option is set, it wouldn’t create them.