Daniel Thwaites

Unfortunately, the majority of Stylix's functionality is not possible without Home Manager due to applications only supporting configuration files within the home directory. It's possible to use without flakes, though.

Personally, I prefer having the options set as they are now, so I'm aware of any conflicts. This is most relevant when Stylix needs to set more than one option...

> IMHO, it would be more structured to add this functionality under an [options.stylix.targets.hyprland.wallpaper](https://github.com/danth/stylix/blob/81df8443556335016d6f0bc22630a95776a56d8b/modules/hyprland/hm.nix) option, although we might change the wallpaper option name. I agree, this should be combined with...

IMO, hyprpaper is less of a target itself, and more just the means of theming hyprland. So ideally they should use the same option to enable both.

> This is wrong, hyprpaper works perfectly well as a standalone service for all wlroots-based compositors. It should be a separate target. Depends whether we're only setting it up when...

That would also be helpful, although a check in code will also catch cases where someone didn't read the docs.

I agree, the version stored in our `flake.lock` should be guaranteed to work perfectly. We still need to support people using slightly newer / older revisions to some extent, since...

AFAIK that action doesn't trigger the GitHub Actions checks, since events caused by an Actions workflow can't trigger another workflow, so reviewing it's PRs would be inconvenient.

Built in support for wallpapers on Hyprland is being worked on in #377

AFAIK scripts will generally send `SIGTERM` whereas terminals will generally send `SIGINT`, so Nix could have different behaviour when it's running interactively. Perhaps less confusingly, it could use an alternative...