You should be able to setup WSLg then run the Linux Codium in WSL. Regular VS Code will work that way, it just gives a little “hey, you know you could use remote WSL right?” message then keeps chugging.
The benefit of the WSL (and SSH and Docker) integration is that you still run the native version of VS Code for your OS, and just the server portion of VS Code runs on the ‘remote’ server. Running the whole of VS Code (or Codium or whatever) in WSL probably works but there’ll be little annoying things with it since it’s not running natively, for example you can’t drag files from Explorer into it, can’t have a PowerShell terminal open alongside a WSL one, etc.
I don’t think the SSH integration is locked down, so I wonder if you could install OpenSSHd in WSL and connect vis SSH.
For sure the remote extension option is better, just wanted to let TwinHaelix know the native Linux version is an option if the extension can’t be loaded.
can’t have a PowerShell terminal open alongside a WSL one, etc.
How are you getting this to work? According to only the default profile can be opened with the local integrated terminal. The default profile seems to be bash, so that fails. But I wouldn’t want set my default profile to PowerShell when I’m in WSL.
when I install codium (with yay, because I use Arch… btw) there is a package that just makes the plugin store the same as Microsoft’s. I found one that wasn’t working and that was MS pylance, I use pyright now.
I really wish the WSL extension wasn’t locked behind VS Code. My workflow is heavily reliant on it which locks me into the proprietary IDE.
You should be able to setup WSLg then run the Linux Codium in WSL. Regular VS Code will work that way, it just gives a little “hey, you know you could use remote WSL right?” message then keeps chugging.
Is WSLg on Win10 yet?
Yep. I have it running with an Intel integrated graphics chips. There was a driver I had to download direct from Intel instead of HP, though.
https://github.com/microsoft/wslg
https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps
https://devblogs.microsoft.com/commandline/the-windows-subsystem-for-linux-in-the-microsoft-store-is-now-generally-available-on-windows-10-and-11/
The benefit of the WSL (and SSH and Docker) integration is that you still run the native version of VS Code for your OS, and just the server portion of VS Code runs on the ‘remote’ server. Running the whole of VS Code (or Codium or whatever) in WSL probably works but there’ll be little annoying things with it since it’s not running natively, for example you can’t drag files from Explorer into it, can’t have a PowerShell terminal open alongside a WSL one, etc.
I don’t think the SSH integration is locked down, so I wonder if you could install OpenSSHd in WSL and connect vis SSH.
For sure the remote extension option is better, just wanted to let TwinHaelix know the native Linux version is an option if the extension can’t be loaded.
How are you getting this to work? According to only the default profile can be opened with the local integrated terminal. The default profile seems to be bash, so that fails. But I wouldn’t want set my default profile to PowerShell when I’m in WSL.
when I install codium (with yay, because I use Arch… btw) there is a package that just makes the plugin store the same as Microsoft’s. I found one that wasn’t working and that was MS pylance, I use pyright now.
What’s the package called? Am on nix but might look into it later
you lucky bastard, I just so happen to take a screenshot when I set it up
Ah fantastic thank you
Your welcome!
For blind people: it’s called aur/vscodium-bin-marketplace.
Right, sorry and thanks.
Have you tried manually installing it?