vscode-vagrant VS openvsx

I'm sure it does fine at that, but there are perils with SSHFS-type access (like corruption when you switch from machine to machine

And this really doesn't get close to what Visual Studio Code's Remote editing functionality can do if the machine/container can support node. The Remote mode operates a full remote VSC environment over SSH or as a docker container, and that means things like being able to do find and replace at the remote end in the editor, but also manage git at the remote end using the built-in source control etc.

I too cannot imagine going back to an editor that cannot do this. It has been so useful in conjunction with vagrant boxes, with a bit of ssh_config magic I wrote here that manages an ssh_config include file that (amazingly) VSC will follow:

(warning: ugly)

https://github.com/bbenoist/vscode-vagrant/issues/18#issueco...

The following are some of the most common extension types on the Visual Studio Code Marketplace and Open VSX Registry, an open-source, community-driven extension registry for Visual Studio Code (VS Code) extensions.

Eclipse runs the Open VSX registry that VS Codium uses. Eclipse also has a fork of VS Code called Theia.

https://open-vsx.org/

https://theia-ide.org/

The extension is not available on https://open-vsx.org/ ? (The market place for VSCodium)

See also: https://open-vsx.org

Would you consider supporting the open vsx repo in your release workflow for those of us on VSCodium?

I didn't know about https://open-vsx.org/. Very nice! But besides those languages, they are also missing things like the remote ssh extension, which is a big deal breaker for me (and I assume many others regardless of language).

Any chance you could publish it to Open VSX as well, for the people not using the Microsoft version?

no there's lots of extensions available on vscodium, just not the same ones (https://open-vsx.org)

If we do not generate enough interest, we’ll be forced to decommission https://open-vsx.org/ by the end of May, 2023