It’s a snap problem, not actually a VS Code issue. Just another reason why snap is bad.
Funny how it’s only a problem when using the Snap distribution.
Friendly reminder that VSCodium exists, and nobody should be using Microslop’s spyware version anyway.
Friendly reminder, that Emacs exists.
Been using zed lately. Pretty similar ui, wildly different performance.
VSCodium would have the same Electron caching issues though, wouldn’t it?
The only difference really is the occasional extension that needs a manual install.
I’ve been trying out VSIX Manager for my extensions so that I can keep track of which ones I want to install on each machine. This can make it easier to install the weird extensions that you can’t install otherwise
I tried open vss I think it’s called on arch and I have trouble using it to remotely access configs on my home server via the SSH extension. I got fed up with it and installed the MS version from yay. I resent it but it works.
I think the open version might not have the ms extension store configured. There should be a separate AUR package for that. At least there is for VSCodium. Alternately you can just grab the VSIX for the extensions you want from the MS version and install them on the open one. Personally I don’t know what open vss is so I use codium.
Oh nice, I didn’t know, thank you!
My favorite fun fact about VSCode is it stores all its cache files in
$XDG_CONFIG_HOME.Yay, it uses the XDG dirs… Wait, no, not like that.
If you are on Linux, use a real editor like Vim or Emacs and not… THAT
Help, how do I get out!!!
/s
There IS no leaving. If you are IN, you STAY IN.
Microsoft managing to make even their Linux software not achieve basic functions like…deleting files.
ROCKEY
HORROR
Wha??? A Microsoft product!!! Nooooo… c’mon
