mirror of
https://github.com/nix-community/home-manager.git
synced 2025-12-04 08:01:02 +01:00
281e9398cc
With swayidle one can configure two different kinds of hooks:
- Idle timeouts are executed after the session has been idle for a
specific amount of time.
- Events are executed when systemd notifies us that for example the
user session is locked or that the device is about to suspend.
While not obvious, there is a significant difference between how these
two kinds are configured: there can be several timeouts with separate
commands to be executed, but each event can only be specified once. If
an event is specified multiple times, then the last command wins.
This can be very easy to miss in swayidle's documentation. Furthermore,
because the config is a list of `{ event = "..."; command = "..."; }`
attrset, we double down on this confusion and make it seem like having
multiple handlers for an event was actually supported.
Fix this by converting from a list of "event" submodules to an attrset
where the key is the event name and the value is the command to be
executed. This makes it impossible to specify multiple commands for a
single event by accident.
If a user _does_ want to have multiple commands executed on any event
they can for example use `pkgs.writeShellScript` and manually chain the
commands in that script.
|
||
|---|---|---|
| .. | ||
| accounts | ||
| config | ||
| files | ||
| i18n/input-method | ||
| launchd | ||
| lib | ||
| lib-bash | ||
| misc | ||
| po | ||
| programs | ||
| services | ||
| targets | ||
| dbus.nix | ||
| default.nix | ||
| deprecations.nix | ||
| files.nix | ||
| home-environment.nix | ||
| manual.nix | ||
| modules.nix | ||
| systemd-activate.sh | ||
| systemd.nix | ||
| wayland.nix | ||
| xresources.nix | ||
| xsession.nix | ||