Tim Pope

This is a reasonable goal, but I don't think hard coding a color is a good practice, and I'm not sure what to link it to.

Removing `markdownLineStart` from the `contains` on `markdownLinkText` seems to fix it. Can you try that for a week and report back as to whether that causes any problems?

And if there aren't any issues, a pull request would be great.

I spent a lot of time tinkering with this particular edge case before I gave up. Markdown is just too expressive to highlight with regexes alone, and regexes is all...

Fenced code blocks go against the spirit of Markdown (readable plain test), so I will not be adding an option that in any way implies an endorsement of them. I...

Yes, it's a compromise with code blocks. Triply nested lists are extremely rare (as in I've never seen one in the wild), but I'd entertain extending it to 8 spaces...

The triple backtick syntax is nonstandard (and kinda gross and ugly imho). But the blank line compromise might be serviceable, although I'm not sure how feasible it would be to...

It's just `'formatoptions'`. The problem is that fixing one behavior tends to break another.

۱. list ۲. test Based on the above, GitHub flavored Markdown at least does not appear to support this. Can you name an implementation that does? > also something like...

Guessing from the error message it's this line: https://github.com/tpope/vim-fireplace/blob/2e4540d62fd49523a3aefeab896a33ed6bbcb43b/autoload/fireplace.vim#L1366 You could try putting `:echo json_encode(state)` right above that line to see what's in that data structure.