Spyke

Accent colors are now a standard preference for Linux

Accent colors provide a way for users to personalize their desktop in a simple, developer-friendly, and effective way. Throughout the community there has been a general interest in the inclusion of accent colors within apps and desktop environments. This proposal aims to standardize an accent color key on the Settings portal.

A new key on the Settings portal, accent-color, would be defined under the org.freedesktop.appearance namespace.

Via @[email protected]

And endorsed by #GNOME, #KDE, #CosmicDE, #ElementaryOS, and #Budgie, at that!

Accent colors are now a standard preference for Linuxhttps://github.com/flatpak/xdg-desktop-portal/pull/815Open linkView original on lemmy.ndlug.org
lemmy.world

Nice. This feature is similar to Android wallpaper color theming.

And I thought Xorg already had this feature in Xresources, but apps do not respect it.

46

The setting being located somewhere is never the hard part, it’s all about the different communities respecting it.

40

Nice! I recently switched to Android and the Material You adaptive coloring through the system is so nice.

Anything that makes customizing a Linux desktop a little easier is good in my book.

39
sh.itjust.works

So now we are going to get an 'accent-color' pref in flatpaks or flatpaks finally will follow color-schemes?

25
lemmy.world

A setting was added that all applications can read and soon desktops which have color schemes will set it.

9
lemmy.ml

For what I just read in the github discussion and in the linked gnome discussion is not endorsed by Gnome, as you can see here

9

Huh that sounds stupid, I wonder how arbitrary colors would make the feature substantially harder to implement on their side. I never developed for either KDE or GNOME, but the workarounds given sounded super reasonable to ne

2
lemmy.ca

Yep Linus got embarrassed that this feature has been missing all these years, so now you can get custom accents on kernel panics.

38
Salixreply
sh.itjust.works

Isn't this a separate package not part of the Linux kernel? I don't see why Linus would have to get involved.

25
lemmy.world

They are being overly semantic about what “Linux” means. Obviously this is about desktop projects.

32
Salixreply
sh.itjust.works

They said "Linus", not "Linux".

I was assuming they thought Linus Torvalds was the one working on merging this.

1
russjr08reply
outpost.zeuslink.net

Yes, but I think the implication of the supposed semantics is that if we're only ever referring to "Linux" as the kernel itself, then Linus possibly would've seen it.

Not sure if he would've merged it, my knowledge of the kernel development process is a bit lacking - but I thought all the various subsystems of the kernel had their own maintainers who handled merging patches.

3
Salixreply
sh.itjust.works

Not sure if he would’ve merged it, my knowledge of the kernel development process is a bit lacking - but I thought all the various subsystems of the kernel had their own maintainers who handled merging patches.

Per this:

https://www.kernel.org/doc/html/latest/process/2.Process.html#how-patches-get-into-the-kernel

There is exactly one person who can merge patches into the mainline kernel repository: Linus Torvalds.

When the merge window opens, top-level maintainers will ask Linus to "pull" the patches they have selected for merging from their repositories. If Linus agrees, the stream of patches will flow up into his repository, becoming part of the mainline kernel.

While there are top level maintainers for the subsystems, it looks like Linus is the only one who can merge them into the mainline kernel.

5

You reached the end

Accent colors are now a standard preference for Linux | Spyke