You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be one clear way of doing things, fenced code block are already the primary way of adding a code block
explicit is better than implicit, fenced code blocks provide a much more explicit indication of the code block
indented code block enforce a lot of technical limitations for the syntax/parser
As an example, you can look at https://markdown-it.github.io/ compared to https://djot.net/playground/ (a proposed successor to commonmark).
In djot it is perfectly fine to indent syntax blocks with any number of spaces, without having it become a code block
::::admonition
:::admonition
s
:::
::::
This would be a breaking change from CommonMark, but one that should be possible
The text was updated successfully, but these errors were encountered:
100% support. Actually probably going towards a "subset" of CommonMark like djot in some regards (i.e. one where certain things just don't work because they're ugly/confusing) is nice. We won't miss indented code blocks. Having come from an rst background, that was the worst bit :D
As discussed in https://johnmacfarlane.net/beyond-markdown.html (the creator of Markdown)
As an example, you can look at https://markdown-it.github.io/ compared to https://djot.net/playground/ (a proposed successor to commonmark).
In djot it is perfectly fine to indent syntax blocks with any number of spaces, without having it become a code block
This would be a breaking change from CommonMark, but one that should be possible
The text was updated successfully, but these errors were encountered: