Markdown Support for Visual Studio CodeAll you need for Markdown (keyboard shortcuts, table of contents, auto preview and more). Note: VS Code has basic Markdown support out-of-the-box (e.g, Markdown preview), please see the official documentation for more information. Table of Contents
FeaturesKeyboard shortcuts
See full key binding list in the keyboard shortcuts section Table of contents
List editingNote: By default, this extension tries to determine indentation size for different lists according to CommonMark Spec. If you prefer to use a fixed tab size, please change the Print Markdown to HTML
GitHub Flavored Markdown
MathPlease use Markdown+Math for dedicated math support. Be sure to disable Auto completionsTip: also support the option
Others
Available Commands
Keyboard ShortcutsTable
1. If the cursor is on a list/task item without selection, strikethrough will be added to the whole item (line) Supported SettingsTable
FAQQ: Error "command 'markdown.extension.onXXXKey' not found"
Q: Which Markdown syntax is supported?
For other Markdown syntax, you need to install the corresponding extensions from VS Code marketplace (e.g. Mermaid diagram, emoji, footnotes and superscript). Once installed, they will take effect in VS Code and also the exported HTML file. Q: This extension has overridden some of my key bindings (e.g. Ctrl + B, Alt + C)You can easily manage key bindings with VS Code's Keyboard Shortcuts editor. (Commands provided by this extension have prefix Q: The extension is unresponsive, causing lag etc. (performance issues)From experience, there is a good chance that the performance issues are caused by other extensions (e.g., some spell checker extensions). This can be verified if you try again with all other extensions disabled (execute To find out the root cause, you can install our development build ( ChangelogSee CHANGELOG for more information. Latest Development BuildDownload it here, please click the latest passing event to download artifacts. There are two versions: To install, execute Contributing
Special thanks to the collaborator @Lemmingh and all other contributors. Related |