-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
Support GitHub-style backtick math syntax in Markdown #208430
Comments
Totally agree with this, it is so annoying that I can't use the same syntax for vscode markdown and github. |
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Very annoying issue particularly when you want to put some formulae in your markdown. A little bit inconvenient to always push to GitHub to see what happens |
🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Any update on this please? Another workaround, by the way, is to use |
GitHub and VS Code both render math within dollar signs, but GitHub has some known bugs when rendering math like this, such as omitting curly braces. One workaround is to double up on backslashes, but VS Code interprets these as line breaks. A more general solution is to use GitHub's alternative syntax which nests backticks inside of the dollar signs, but VS Code does not support that syntax, resulting in extraneous apostrophes.
$A = \{4, 2, 1, 3\}$
$A = \\{4, 2, 1, 3\\}$
$`A = \{4, 2, 1, 3\}`$
Thus, as far as I'm aware there is currently no way to author Markdown math in VS Code such that the preview shows what GitHub will eventually render. It would be nice if VS Code supported the same backtick math syntax that GitHub supports, especially since it is already also supported by other platforms like GitLab.
The text was updated successfully, but these errors were encountered: