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 theorg.freedesktop.appearancenamespace.
And endorsed by #GNOME, #KDE, #CosmicDE, #ElementaryOS, and #Budgie, at that!
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.
The setting being located somewhere is never the hard part, it’s all about the different communities respecting it.
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.
So now we are going to get an ‘accent-color’ pref in flatpaks or flatpaks finally will follow color-schemes?
A setting was added that all applications can read and soon desktops which have color schemes will set it.
Oh, thanks! Will gnome apps follow this as well?
Eventually. I don’t think libadwaita supports accents yet.
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
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
Computer, go to red accent
That’s good to hear!
So Linus finally merged this?
Yep Linus got embarrassed that this feature has been missing all these years, so now you can get custom accents on kernel panics.
Finally we can get Blue 🔵 screen of death in Linux
@A10
@BeigeAgenda
Where Windows fails, Linux takes it’s place
( ꈍᴗꈍ)
Isn’t this a separate package not part of the Linux kernel? I don’t see why Linus would have to get involved.
They are being overly semantic about what “Linux” means. Obviously this is about desktop projects.
Cue “what you are calling Linux is actually” copypasta
Linus/Linux or as I’ve recently taken to calling it…
They said “Linus”, not “Linux”.
I was assuming they thought Linus Torvalds was the one working on merging this.
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.
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.
Ah, makes sense! That’s a great read, I’ve been meaning to read more into their development process!
I was thinking 🤔 the same before I opened the link.
