We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In order to get a fenced code block to be recognized by Markdown Extended, you must leave a blank line before the opening marker, like this:
some text ``` x = 5 # some code ```
The blank line is not actually required by GFM. GFM actual spec. Compare to e.g., the MarkdownEditing > Markdown GFM Sublime syntax.
MarkdownEditing > Markdown GFM
(On the plus side, the backticks are actually recognized as a separate scope available to be styled. Yay!)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In order to get a fenced code block to be recognized by Markdown Extended, you must leave a blank line before the opening marker, like this:
The blank line is not actually required by GFM. GFM actual spec. Compare to e.g., the
MarkdownEditing > Markdown GFM
Sublime syntax.(On the plus side, the backticks are actually recognized as a separate scope available to be styled. Yay!)
The text was updated successfully, but these errors were encountered: