-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
[Wofi] Unable to add css style #891
Comments
I can't reproduce this, could you share your config? This is really weird cause strings should be merged not conflict. |
In my home.nix : programs.waybar = {
enable = true;
# some settings options, nothing too scary...
style = /* css */ ''
* {
border-radius: 0;
box-shadow: none;
}
/* other css... */
'';
};
programs.wofi = {
enable = true;
style = /* css */ ''
* {
border-radius: 0;
}
'';
}; However, the waybar style gets merged correcly (and firefox...). Wofi is the only one. I'll maybe put my edited config in a gh repo when I have time (the current one is old) |
Btw I have configured stylist only on the NixOS side, not home manager. But it used to work. |
Is this issue a duplicate of #481? |
Nope, the expected behavior is for redefining |
@freerig it's hard to offer much support without your full config.
clearly stylix is important as a hm module, cause |
I think this is vaguely what the previously mentioned issue is about. Either way, extending Stylix options is currently not always possible because we are generating our own configuration files, instead of integrating with the Nix options of other frameworks, like Home Manager or NixOS. Note that resolving this is part of the roadmap. |
Works fine on waybar, and should also work for wofi. Nix should merge the stylix config with the user's config. |
Ok see my config at https://codeberg.org/nyxer/computer-machine |
Hi,
Nix says
'programs.wofi.style' has conflicting definition values
because I set my own css. I triedlib.mkAfter
andlib.mkBefore
but still got the same problem. I don't want to override Stylix's css.Is the problem Stylix or me ?
The text was updated successfully, but these errors were encountered: