Besides VSCodium (which isn’t really a fork, it’s just building from the source code of VSCode without the Microsoft stuff), there aren’t any VSCode forks/derivatives that aren’t AI-assisted editors (see Cursor, Windsurf, those are the main two, right?).
That feels a bit weird to me, as many other pieces of software have lots of forks and derivatives (browsers, operating systems, email clients, emulators, PDF viewers, Fediverse clients, etc.). I guess people who would bother to create a fork and doesn’t want to put AI in everything just uses a different editor.
There’s nothing wrong with VSCodium, it’s awesome. My only gripe with it is that the rpm package takes ages to update compared to everything else I use, which is weird. Other than that issue, it runs fine, and I like the flexibility that plugins give me. I just find it odd that there aren’t any other VSCode derivatives/forks.
Oh, I thought you meant one of those file tree sidebars was white.
Does the file picker look somewhat like this?
Then it’s using the KDE file picker. I believe, it should be possible to make it use the GTK file picker, by configuring the “desktop portal” correctly.
Here is a guide for doing the reverse of what you need (GTK application in KDE Plasma): https://wiki.archlinux.org/title/Uniform_look_for_Qt_and_GTK_applications#Consistent_file_dialog_under_KDE_Plasma
Maybe you can do the steps the other way around or it helps you find a better guide…
And no problem. 🙂
Yep, that’s it. I’ll look at that soon, thanks!