3 ms·
https://myst-parser.readthedocs.io/en/latest/syntax/syntax.html#show-backticks-inside-raw-markdown-blocks https://myst-parser.readthedocs.io/en/latest/syntax/sy
by mdaniel 4y ago
https://myst-parser.readthedocs.io/en/latest/syntax/syntax.html#show-backticks-inside-raw-markdown-blocks https://myst-parser.readthedocs.io/en/latest/syntax/syntax.h... is excellent, and one of my major pain points. I usually give up and just use ` when I need to talk about backticking in markdown but that idea is much, much better
but I think https://myst-parser.readthedocs.io/en/latest/syntax/syntax.html#comments https://myst-parser.readthedocs.io/en/latest/syntax/syntax.h... is misguided; AFAIK <!-- commentary --> is legal in markdown and far less likely to surprise someone, both with an abnormal comment character as well as the forced block break
- uranusjr 4y agoThe “one more backtick” syntax is a very early Markdown feature explicitly mentioned by John Gruber (originally only for inline code, of course). It might even be in the original “spec”, I don’t remember, but it dates way back and is implemented by virtually all half-decent Markdown parsers. It’s one of the least utilised feature, however, so huge kudos for MyST to clearly explain it and raise awareness.