Hacker News new | ask | show | jobs
by TheRealPomax 102 days ago
GFM, because HTML in markdown should not be a parse error, and getting twenty different markdown "specs" to all agree on new syntax for bits they are obviously missing (like details, classed scoping, transclusions, etc) is not happening.
1 comments
masfuerte 102 days ago
HTML in markdown has never been a parse error. Unless you're using something very broken.

https://daringfireball.net/projects/markdown/syntax#html

link
TheRealPomax 101 days ago
Except under GFM, html is explicitly part of the spec[1], not just "it's not a parse error, but that's because it's just text that doesn't fall in any predefined markdown syntax category", and good luck finding a WYSIWYG markdown editor that gets them right. The number of editors that completely break on <details> alone is disheartening.

[1] https://github.github.com/gfm/

link
abmmgb 101 days ago
I was actually thinking for going with GFM seems popular with many, despite the occasional strong opinions against it..
link