You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The order in which profiles are defined within kanshi's configuration file matters, however since kanshi.nix implements profiles as an attribute set that is converted to a list via mapAttrsToList, profiles within the resulting config file are ordered alphabetically according to their name.
It would likely make sense to convert the profiles option to a list, moving the profile name to an attribute within profileModule, but this would be a breaking change and I'm not familiar with home-manager's policy on this.
Looking at how kanshi defines profiles and that profile names are optional. I think it makes sense to use a list as suggested.
On the other hand, I do not know how configuration changes like this shall be handled.
Shall we put both profiles and profilesList with an assertion that both shall not be used at once and a deprecation message on profiles?
Are you following the right branch?
Is there an existing issue for this?
Issue description
The order in which profiles are defined within kanshi's configuration file matters, however since
kanshi.nix
implementsprofiles
as an attribute set that is converted to a list viamapAttrsToList
, profiles within the resulting config file are ordered alphabetically according to their name.It would likely make sense to convert the
profiles
option to a list, moving the profile name to an attribute withinprofileModule
, but this would be a breaking change and I'm not familiar with home-manager's policy on this.Maintainer CC
@nurelin
System information
The text was updated successfully, but these errors were encountered: