For me, VSCode keeps screwing up file encodings in a legacy project i maintain. I tell it not to autoguess the encoding and define a specific encoding to use. VSCode ignores that and keeps autoguessing.
VSCodium honors the settings (and is a wee bit more private and open-source).
AFAIK you can download every extension as vsix file from vs code web marketplace and then import it into VSCodium. That's how I have been installing missing extensions so far and it works well.
9 Comments
Falst@lemmy.world · 10 pts · 2y
I believe part of what makes the VS Code experience is the extension store. Is this managed in some way with this distributed flavor ?
slampisko@czech-lemmy.eu · 20 pts · 2y
I'm using VSCodium daily and most extensions work, with the notable exception of official MS-published extensions, which mostly require VSCode.
0x0@programming.dev · 3 pts · 2y
This might help.
For me, VSCode keeps screwing up file encodings in a legacy project i maintain. I tell it not to autoguess the encoding and define a specific encoding to use. VSCode ignores that and keeps autoguessing.
VSCodium honors the settings (and is a wee bit more private and open-source).
FrameXX@discuss.tchncs.de · 4 pts · 2y
AFAIK you can download every extension as vsix file from vs code web marketplace and then import it into VSCodium. That's how I have been installing missing extensions so far and it works well.
somegeek@programming.dev · 0 pts · 2y
Works perfectly
somegeek@programming.dev · 5 pts · 2y
Been only using VSCodium for years. Really flawless.
dallen@programming.dev · 3 pts · 2y
Been using the flatpak, works great!
Lodra@programming.dev · 1 pts · 2y
Feel free to share in !vscode@programming.dev!
adept@programming.dev · 1 pts · 2y
Thanks for the reminder. I've been meaning to switch for a while now but I never got to it