[GH-ISSUE #14] setext_with_atx_closed not available in Virtual Studio Code extension #9

New issue

Closed

opened 2026-03-03 01:22:59 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 01:22:59 +03:00

Owner

Originally created by @ghost on GitHub (Feb 28, 2016).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/14

I just installed the markdownlint extension in VS Code. I was going nuts trying to figure out why I couldn't get the .json config to take setext_with_atx_closed, when all the other options (including setext_with_atx) worked fine. So I stumbled on your commit history and see you've only just implemented it. I assume, then, that this change has not been migrated into the VS Code extension. Will you be updating the extension soon, or should it be already working?

To reproduce the symptom:

Create file .markdownlint.json in project folder with the following content:

{
    "MD003": { "style": "setext_with_atx_closed" }
}

In VS Code with markdownlint extension installed, open the project folder.
Create a new file, set its language to Markdown, and enter the following lines:

Test of VS Code 'markdownlint' Extension
==

Setext Header
--

## ATX Header

### ATX_Closed Header ###

Some text.

Observe that all headers are flagged with warnings for rule MD003. Presumably, the setext_with_atx_closed value for the style property is unknown to the extension.

Originally created by @ghost on GitHub (Feb 28, 2016). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/14 I just installed the markdownlint extension in VS Code. I was going nuts trying to figure out why I couldn't get the .json config to take setext_with_atx_closed, when all the other options (including setext_with_atx) worked fine. So I stumbled on your commit history and see you've only just implemented it. I assume, then, that this change has not been migrated into the VS Code extension. Will you be updating the extension soon, or should it be already working? To reproduce the symptom: - Create file .markdownlint.json in project folder with the following content: ``` { "MD003": { "style": "setext_with_atx_closed" } } ``` - In VS Code with markdownlint extension installed, open the project folder. - Create a new file, set its language to Markdown, and enter the following lines: ``` Test of VS Code 'markdownlint' Extension == Setext Header -- ## ATX Header ### ATX_Closed Header ### Some text. ``` - Observe that all headers are flagged with warnings for rule MD003. Presumably, the `setext_with_atx_closed` value for the `style` property is unknown to the extension.

kerem

2026-03-03 01:22:59 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:22:59 +03:00

Author

Owner

@DavidAnson commented on GitHub (Feb 28, 2016):

Your theory is correct: support for setext_with_atx_closed is not yet part of a markdownlint release (and therefore not part of a vscode-markdownlint release).

More context: The most recent tag and "Update to version x.y.z" commit correspond to 0.1.1 which is the latest package in npm. setext_with_atx_closed was added after that and therefore not available yet.

I'll update soon and this will show up in vscode-markdownlint. Sorry for the trouble!

@DavidAnson commented on GitHub (Feb 28, 2016): Your theory is correct: support for setext_with_atx_closed is not yet part of a markdownlint release (and therefore not part of a vscode-markdownlint release). More context: The most recent tag and "Update to version x.y.z" commit correspond to 0.1.1 which is the latest package in npm. setext_with_atx_closed was added after that and therefore not available yet. I'll update soon and this will show up in vscode-markdownlint. Sorry for the trouble!

kerem commented

2026-03-03 01:23:00 +03:00

Author

Owner

@ghost commented on GitHub (Feb 29, 2016):

Very good, thank you!

Just so you know, the reason I missed that this option wasn't released yet was that I followed the link from the VS Code warning light bulb straight to Rules.md in this repo, which of course you've already updated. This being my first time ever on GitHub (or BitBucket, SourceForge, etc.–I'm a dinosaur), it didn't occur to me that this could be a project in active development and the help link might go to not-yet-released documentation. I suppose such leading-edge-of-development glitches are commonplace for developers today, though, so I'll know better next time.

@ghost commented on GitHub (Feb 29, 2016): Very good, thank you! Just so you know, the reason I missed that this option wasn't released yet was that I followed the link from the VS Code warning light bulb straight to **Rules.md** in this repo, which of course you've already updated. This being my first time ever on GitHub (or BitBucket, SourceForge, etc.–I'm a dinosaur), it didn't occur to me that this could be a project in active development and the help link might go to not-yet-released documentation. I suppose such leading-edge-of-development glitches are commonplace for developers today, though, so I'll know better next time.

kerem commented

2026-03-03 01:23:00 +03:00

Author

Owner

@DavidAnson commented on GitHub (Feb 29, 2016):

Thanks for the details. What I'll do with the next vscode-markdownlint release is lock it to the version of Rules.md that corresponds to the version of markdownlint it's using. Sorry for not thinking to do so in the first place!

@DavidAnson commented on GitHub (Feb 29, 2016): Thanks for the details. What I'll do with the next vscode-markdownlint release is lock it to the version of Rules.md that corresponds to the version of markdownlint it's using. Sorry for not thinking to do so in the first place!

kerem referenced this issue

2026-03-03 01:30:13 +03:00

[PR #9] [MERGED] Mention markdownlint-cli in Related section of README.md #801

kerem referenced this issue

2026-03-07 20:09:54 +03:00

[PR #9] [MERGED] Mention markdownlint-cli in Related section of README.md #2650