Skip to content
New issue

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

Use the default Markdown Sublime syntax #157

Closed
sharkdp opened this issue May 25, 2018 · 0 comments
Closed

Use the default Markdown Sublime syntax #157

sharkdp opened this issue May 25, 2018 · 0 comments

Comments

@sharkdp
Copy link
Owner

sharkdp commented May 25, 2018

Apparently, the default Markdown syntax from sublimehq/Packages is quite good (see trishume/syntect#156 (comment)).

I was reluctant to move away from sublime-markdown-extended because I thought that fenced code blocks would not be highlighted properly. However, this was just me using whitespace between opening fences ``` and the language definition (see sublimehq/Packages#1615 and sublimehq/Packages#1616). We should consider to move, should the upstream ticket be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant