this post was submitted on 04 Sep 2023
89 points (96.8% liked)

Programming

17374 readers
379 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Falst@lemmy.world 9 points 1 year ago (3 children)

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 points 1 year ago (1 children)

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 points 1 year ago

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 points 1 year ago* (last edited 1 year ago)

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 points 1 year ago

Works perfectly