-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
stylix: improve stylix.mkEnableTarget
behaviour
#400
Comments
The feh module checks for certain window managers since these are known to not come with their own wallpaper program, and are based on X rather than Wayland, so feh is a suitable all-round solution to install for these cases. I'm not completely sure what the goal of this issue is. Are you suggesting the argument to |
Makes sense. However, with XWayland being a thing, it would make sense to enable it also on Wayland. For example, I use
Essentially, the goal is to resolve the following issue:
Actually, I don't have a concrete suggestion yet. I only noticed the inconsistency, but have not investigated it any further yet. |
See this comment for my suggestions. |
Simplify the 'stylix.mkEnableTarget' documentation. The following issue is to be resolved in danth#400: > Due to some targets not being enabled by default with > 'stylix.mkEnableTarget', the documentation incorrectly generates > 'Default: false' in some cases
Simplify the 'stylix.mkEnableTarget' documentation. The following issue is to be resolved in #400: > Due to some targets not being enabled by default with > 'stylix.mkEnableTarget', the documentation incorrectly generates > 'Default: false' in some cases
What's the status of this now that #244 has been merged? |
For example, #244 changes the
to
which resolves the initial main issue. However, what should we do about the following related issue:
|
Perhaps we should split the Similar to how the GNOME module uses GNOME's built in wallpaper setting, Hyprland uses/will use |
Yes, inverting the dependency chain sounds like a good idea, as it leverages Locality of Behaviour (LoB). Additionally, it simplifies theming Consequently, I suggest adapting all Here is a complete list of all such guards on a7fbda1:
The External Input Support pattern is required to support external modules and is only included for completeness reasons. Is it possible to extend the The remaining listed patterns should be adapted to the |
The first two categories you listed look like they were just missed when I used
For KDE, this exists since we check whether KDE is installed at runtime rather than using its enable option (KDE would be enabled in a NixOS config, but we're using a Home Manager module). When running Home Manager on MacOS, it's impossible for KDE to be installed hence we skip the check. I believe there may also be an error involved due to some of the dependencies not being available on MacOS. For Swaylock, it may be possible to remove the guard since Home Manager should only use the settings when Swaylock is enabled. I haven't tested this. |
About
This is a tracking issue for enabling all Stylix targets by default with
stylix.autoEnable
, and simplifying thestylix.mkEnableTarget
documentation. This behaviour is desired based on the following reasoning:stylix/stylix/target.nix
Lines 17 to 24 in 00a11ba
Currently, some targets are enabled based on unscalable checks. For example,
feh
manually tries a non-exhaustive list of window managers, although the window manager dependency seems wrong in this case:stylix/modules/feh/hm.nix
Lines 4 to 11 in 00a11ba
Due to some targets not being enabled by default with
stylix.mkEnableTarget
, the documentation incorrectly generatesDefault: false
in some cases with #399. Resolving this involves manually extendingdocs/settings.nix
or enabling all targets by default withstylix.mkEnableTarget
.Steps
stylix.autoEnable
mkEnableTarget
documentation #399The text was updated successfully, but these errors were encountered: