Tim Pope

Can you tell me how #16 works for you? I never got around to thoroughly evaluating it.

Yeah this stuff is super flaky and implementation dependent. If you're writing markdown, you should just always escape underscores to be safe. I'm open to improvements in the highlighting but...

Yeah, I can't think of a way to do this short of littering `syntax/html.vim` with a bunch of Markdown exemptions. Markdown is a syntax highlighter's worst nightmare. :/ As a...

I really don't like using `Error` for something that's not an error. Maybe `Underlined` or even `Todo`? Those are both visible for whitespace in the default color scheme.

Or maybe we could set a conceal char. That feels like the most natural way to make it visible.

The second part is a bit trickier. Maybe a negative lookahead for `>`, `/>`, or `[[:alnum:]_-]\+=`? I'll let someone else take a stab.

My guess would be that yes, it could.

So that's an HTML comment, wouldn't this make more sense in the HTML highlighting?

The reason it isn't merged is because it isn't Markdown! Every system I've seen that uses YAML frontmatter accepts HTML along side Markdown, yet I don't see support for it...

> * Technically it is upstream of Markdown and does not mix with it, so it is easy to support without interfering with the core. Easy to add, not easy...