> The 'base16-schemes' package uses the 'tinted-theming/base16-schemes'
> repository, which has now been archived by the owner in favor of
> 'tinted-theming/schemes'
>
> -- https://github.com/NixOS/nixpkgs/issues/285671
Brings the Zellij theme more in-line with the default theme. For dark themes, Zellij's shades go from darkest to brightest: black < bg < fg < white. The exact shades used for the four is based on the standard mapping of the 8 primary colors to ANSI's 4 shades.
This makes the tab and status bars significantly more readable.
This does not account for light themes, and Zellij dynamically switches between white and black for certain elements depending on the polarity, however I couldn't find of other modules that accounted for polarity, so I left it for a future change. I also did not rename the accents to their semantic names, though it would be simple to do.
Remove the obsolete 'fonts.fontDir.enable' option and replace the
'fonts.fonts' option with 'fonts.packages'.
This should fix Stylix for nix-darwin past 58b905ea.
Closes: https://github.com/danth/stylix/issues/435
Initialize the 'hyprpaper' module.
In the future, it might be possible to 'unload' the one-off wallpaper to reduce
the running memory usage [1]:
> Preload does exactly what it says. It loads the entire wallpaper into
> memory. This can result in around 8 - 20MB of mem usage. It is not
> recommended to preload every wallpaper you have, as it will be a)
> taking a couple seconds at the beginning to load and b) take 100s of
> MBs of disk and RAM usage.
>
> Preload is meant only for situations in which you want a wallpaper to
> switch INSTANTLY when you issue a wallpaper keyword (e.g. wallpaper
> per workspace)
>
> In any and all cases when you don't mind waiting 300ms for the
> wallpaper to change, consider making a script that:
> - preloads the new wallpaper
> - sets the new wallpaper
> - unloads the old wallpaper (to free memory)
>
> -- Hyprpaper [2]
[1]: https://github.com/danth/stylix/issues/408
[2]: 678d0e8959/README.md (L103-L111)
Co-authored-by: NAHO <90870942+trueNAHO@users.noreply.github.com>
Add a 'stylix.enable' option to enable or disable all Stylix modules in
order to resolve issues similar to [2].
To align with the default 'lib.mkEnableOption' [1] behavior,
'stylix.enable' defaults to 'false'.
BREAKING CHANGE: Stylix is disabled by default. To enable it, use:
stylix.enable = true;
[1]: https://github.com/NixOS/nixpkgs/blob/23.11/lib/options.nix#L91-L105
[2]: https://github.com/danth/stylix/issues/216
Co-authored-by: Daniel Thwaites <danthwaites30@btinternet.com>
Co-authored-by: Jalil David Salamé Messina <jalil.salame@gmail.com>
Co-authored-by: NAHO <90870942+trueNAHO@users.noreply.github.com>
Simplify the 'stylix.mkEnableTarget' documentation.
The following issue is to be resolved in
https://github.com/danth/stylix/issues/400:
> Due to some targets not being enabled by default with
> 'stylix.mkEnableTarget', the documentation incorrectly generates
> 'Default: false' in some cases
The attrset is used heavily in styllix's modules, but the docs don't contain even a top-level explanation of its value. Though you can gather most it from skimming `base16.nix`, I think stylix should provide an entry point for users, interested in using their color schemes outside of stylix. I base this assumption on personal anecdote of people not having a good understanding of exported values even after extended usage and implementing parallel parsing logic for color scheme files.
