thomaskoppelaar / vscode-markdown-preview-wikilinks

Allows wikilinks features within the VSCode markdown preview.

Markdown Wikilinks Preview

Note: Markdown Notes now has a better version of this, integrated into the extension itself. I would not recommend using this in combination with it.

Allows wikilinks features within the VSCode markdown preview.

Uses a fork of a markdown-it plugin (original here In order to make linking markdown documents a bit more rewarding - The VSCode preview window now also shows wikilinks correctly.

This is still in very early development. If anything goes wrong, submit an issue or a PR.

Features

• Enables highlighting of Wikilinks within the VSCode Markdown Preview. (Works with piped links as well!)
• Allows clicking on those links to go to the referenced file's preview.

Limitations

• When clicking a link inside the preview, only the preview will update; The file won't open in your editor.

• Linking between files with different extensions (e.g. .markdown and .md) Will cause trouble.

  • Currently, this extension will append any link with a .md extension.

• File naming convention is very basic: lowercase-filenames-without-spaces-or-periods will work the best. Anything else is bandit territory.

Roadmap

• User defined settings
  • File type (.markdown, .mdx, etc.)

vscode-markdown-preview-wikilinks's Issues

links are corrupted in preview

with a link [[self\-study notes|p.selfstudy notes]] I should see text "self-study notes" linking to file "selfstudy notes.md", but instead, I see "self\ study notes" (dash is changed to a space... bug #1) linking to "selfstudy-notes.md" (space is changed to a dash, bug #2... the link is broken)

Open VSX Listing: Signing the Publisher Agreement

Thank you for being part of the Open VSX community by adding your extensions to the Open VSX Registry. Please note that the service was recently transferred to the Eclipse Foundation and urgent action on your part is needed so we can continue to list your extensions. To ensure uninterrupted service, please sign the Eclipse Publisher Agreement on or before January 8, 2021. If not signed by that date, your extensions will be delisted and will no longer appear on the site nor be available via the API. If you sign at a later date, your extensions will then be re-activated. The signing process is explained in the Wiki (steps 1 and 2).

Please also note that all extensions MUST have a license in order to be listed.

More details are in these recent blog posts:
https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management
https://blogs.eclipse.org/post/brian-king/new-era-open-vsx-registry

Today, there’s growing momentum around open source tools and technologies that support Visual Studio (VS) Code extensions. Leading global organizations are adopting these tools and technologies. This momentum has spurred demand for a marketplace without restrictions and limitations. Thanks for joining us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!