Installing vscode-r-lsp on VSCodium?

I am pretty new to VSCodium and its extension eco-system, so please bear with me.

I read @renkun-ken’s blog Writing R in VSCode and was inspired to try out the setup described. vscode-R was easily installed, and I already had the languageserver R package, and radian was a very nice surprise as well (thanks for that tip!). But there is no readily apparent way to install vscode-r-lsp.

I run VSCodium, not VSCode, and yes I could probably switch and why do I complicate things… but I like the ethos behind it and really dislike the closed nature and built-in telemetry Microsoft employs. Also, if I understand the situation correctly, Microsoft prohibits non-Visual Studio products from installing any binaries downloaded from their marketplace in its terms of service. So far VSCodium has worked great for me.

I was able to download vscode-r-lsp’s current VSIX file from its VisualStudio Marketplace page but only by manually clicking a link in the browser, as Microsoft’s Marketplace appears to hide the URL of the VSIX link behind Javascript. In any case, there’s still the legal aspect.

If I may suggest, perhaps vscode-r-lsp could do one of the following

• publish VSIX files as Github releases or tags (would work nicely with automation scripts, and for humans too),
• publish to Open VSX (would make the extension available from VSCodium’s built-in extension gallery, just like ikuyadeu.r)
• post instructions on how to build the VSIX file from this published source (would have to be rather detailed 😉

I would love to hear your suggestions or comments. Sorry for opening an issue for such a rather general question.

[phillc73]

This extension is now published in the Open VSX repository:

https://open-vsx.org/extension/REditorSupport/r-lsp

As you can see, the listing says it is published by me, not the verified owner of the namespace.

I have confirmed that installation works correctly in VSCodium v1.52.1

[phillc73]

It seems like there is a reasonably straight forward process for publishing an extension to openvsx. I’d be willing to take on an initial publish of the extension to the Open VSX Registry, and try to insure regular updates for each new version bump.

After reading the docs it appears that publishing an extension on Open VSX does not give me ownership of the namespace, which can be claimed or verified by @renkun-ken or someone else from the REditorSupport group at a later date.

Anyway, what I’m really requesting is permission from the authors to publish this extension to Open VSX, which would then make it available for VS Codium users.