vscode-markdownlint VS obsidian-linter

There is a very impressive Markdown Linter for VSCode markdownlint. It has built in rules that can be several different ways, it also supports custom rules written in JavaScript.

I'm trying to use flycheck with markdown-markdownlint-cli. Running markdownlint-cli2 via shell and the VSCode Markdownlint Plugin are respecting the configuration file, but flycheck doesn't.

I did some searching and found a tool by Victor Tao (not me), called Obsidian Linter, and it got me wondering, have any of you found success using this tool, or something similar? I have been working with it for a minute now, and though a lot of my time right now is spent tweaking the linting options, I feel once I have gotten everything set up the way I need it, this could be quite the game changer for my productivity and note-taking speed.

It turns out that the plugin Linter is able to automatically escape YAML keys that shouldn't be there, including this exact use case, a colon followed by a space. The trouble is that it is not doing it, which I assume means Linter is only parsing the frontmatter YAML for this issue and is not checking the content between ```. Anyone able to point me in the right direction would be greatly appreciated!

This plugin can do exactly what you need. https://github.com/platers/obsidian-linter

Maybe Linter is something for you. I use it to add/remove frontmatter.

And then i use [Linter](https://github.com/platers/obsidian-linter) the remove the "#".

There’s a linter plugin for Obsidian, too.

I use https://github.com/platers/obsidian-linter, which can add the current file name as a header. I create a new file, press CTRL+S or CMD+S to trigger it, and everything is already in place.