Use stdm.

[cirosantilli]

With GitHub + Stack Exchange + Reddit support + 2 reference implementations it will dominate.

http://jgm.github.io/stmd/spec.html

Furthermore, it is currently a good average of existing implementations, and much better specified than the original markdown.

[ilikepi]

Definitely suggest leaving this open for comment for a bit. I'm curious to see if the apparent controversy over the name "Standard Markdown" will get resolved or if it will just fade into the background. The name seems to be the biggest polarizing issue at the moment.

[cirosantilli]

Lol true: http://blog.codinghorror.com/standard-markdown-is-now-common-markdown/

[shirosaki]

Now the name is CommonMark. http://commonmark.org/

[alerque]

(Please see #567 for background on the recent project namespace change.)

This is easily the most interesting open PR — and ironically the oldest. I think this question needs to be decided and not just left hanging because it kind of defines what the plugin is about. A syntax plugin cannot "just work" for all variants out of the box because their are known contradictions and ambiguities. Besides the "original"¹ markdown which is well documented to be incomplete and leave lots to chance, there any a plethora of more refined variants and extensions (GFM and Pandoc flavors probably being the two best known), and of course now there is CommonMark, a standard on which many projects are covering².

Which does this plugin actually target? Is it actually best at what it targets or in practice is it closer to something else? And what other plugins target a more specific variant that we might want to play nice with (@tpope's plugin of the same name comes to mind as well as the @vim-pandoc project's vim-pandoc-syntax.

¹ _{Pandoc recently clarified in their manual that what sometimes used to be termed "standard" markdown is the "original" Grubber issued gig.}

² _{Which also includes an ecosystem of extensions, not all of which are mutually compatible.}