this post was submitted on 09 Jul 2023
104 points (98.1% liked)

Asklemmy

43892 readers
971 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] herrherrmann@lemmy.ml 1 points 1 year ago* (last edited 1 year ago) (1 children)

I started with Notepad++ and some CSS-specific editor (I can’t figure out the name anymore!), then switched to Brackets (RIP), Atom (RIP) and eventually landed at VS Code. I want to use VSCodium, but some of my favorite extensions are missing and their maintainers refuse to add them to the open VSCodium extension registry…

I would also like to try more “native” editors like Nova, but so far I always ran into blockers with it.

Oh, and for working on Markdown files I use the great Typora!

[–] people_are_cute@lemmy.sdf.org 1 points 1 year ago* (last edited 1 year ago) (1 children)

Bruh, you can literally just copy the '%USERPROFILE%.vscode\extensions' folder to the respective VSCodium folder and those extensions will appear on VSCodium as well.

[–] herrherrmann@lemmy.ml 1 points 1 year ago

Even with VS Code and the proprietary VS Code marketplace, I’ve run into compatibility issues with extensions when upgrading VS Code. So, I’m not too keen to start managing extension files manually. And please don’t call my "bruh".