Skip to content

Drop indented code blocks #50

@chrisjsewell

Description

@chrisjsewell

As discussed in https://johnmacfarlane.net/beyond-markdown.html (the creator of Markdown)

  1. There should be one clear way of doing things, fenced code block are already the primary way of adding a code block
  2. explicit is better than implicit, fenced code blocks provide a much more explicit indication of the code block
  3. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions