-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
catppuccin-gtk: fix inconsistent theme name #324265
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems reasonable but my only issue is that now we are deferring from upstream which also adds to the confusion. I mean even I got confused by this, and I've done some work on ctp gtk
We can't really do much there since upstream was archived, but it doesn't make sense to leave it as it is now either as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, added backport to make catppuccin/nix's life a bit easier
Successfully created backport PR for |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/gtk-settings-suddenly-not-applying/47381/13 |
Description of changes
The theme name uses
default
as fallback for tweaks when they aren't set, which not only is not a valid tweak name, but can lead to confusion and inconsistencies.As such, we can either replace
"default"
with"normal"
, or we can just remove tweaks from the theme name if the list is empty.The advantage of the second approach is that users won't have to worry about which tweak name they have to specify by default, which also looks cleaner:
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.