You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for this extension! It was easy to make a custom regex mapper for navigating files with lots of markdown-formatted comments.
Unfortunately, I had to download and install it manually because it is only published on Microsoft's proprietary Marketplace. The problem is that non-Microsoft builds of vscode are not allowed to use Marketplace per its terms of use. See: microsoft/vscode#31168
I personally use Arch Linux's code package, but there are more popular projects like vscodium, theia, gitpod, and others. The solution these projects use is the Open VSX Registry, an Eclipse Foundation project to provide a vendor-neutral extension repository for vscode-compatible editors.
There is documentation for publishing an extension available. If you're really opposed to that, it's possible to have openvsx auto-publish if the extension is added to their list. But then that list has to be maintained independently of the extension project and is not ideal, so proper publishing is preferred.
Thanks for supporting FLOSS!
The text was updated successfully, but these errors were encountered:
Thank you for this extension! It was easy to make a custom regex mapper for navigating files with lots of markdown-formatted comments.
Unfortunately, I had to download and install it manually because it is only published on Microsoft's proprietary Marketplace. The problem is that non-Microsoft builds of vscode are not allowed to use Marketplace per its terms of use. See: microsoft/vscode#31168
I personally use Arch Linux's
code
package, but there are more popular projects like vscodium, theia, gitpod, and others. The solution these projects use is the Open VSX Registry, an Eclipse Foundation project to provide a vendor-neutral extension repository for vscode-compatible editors.There is documentation for publishing an extension available. If you're really opposed to that, it's possible to have openvsx auto-publish if the extension is added to their list. But then that list has to be maintained independently of the extension project and is not ideal, so proper publishing is preferred.
Thanks for supporting FLOSS!
The text was updated successfully, but these errors were encountered: