Matthieu Coudron 3d65009eff waybar: remove modules-* from defaults ... Some prefer to handle modules-* imperatively for more flexibility, e.g., via waybar "includes" (https://github.com/Alexays/Waybar/wiki/Configuration). Current HM defaults modules-* to `[]` instead of null for most other settings, so they get written to ~/.config/waybar/config even though no explicit configuration has been made. And they take precedence over the imperative ones because of how waybar's includes work: ==== Paths to additional configuration files. Each file can contain a single object with any of the bar configuration options. In case of duplicate options, the first defined value takes precedence, i.e. including file -> first included file -> etc. Nested includes are permitted, but make sure to avoid circular imports. For a multi-bar config, the include directive affects only current bar configuration object. ====		2024-06-09 13:14:04 +02:00
..
default.nix	waybar: allow using attrs for settings (#2547)	2021-12-19 00:21:15 -05:00
deprecated-modules-option.nix	waybar: remove modules-* from defaults	2024-06-09 13:14:04 +02:00
settings-complex-expected.json	waybar: remove modules-* from defaults	2024-06-09 13:14:04 +02:00
settings-complex.nix	waybar: allow using attrs for settings (#2547)	2021-12-19 00:21:15 -05:00
settings-with-attrs.nix	waybar: allow using attrs for settings (#2547)	2021-12-19 00:21:15 -05:00
styling-expected.css	waybar: add module	2020-08-14 00:20:49 +02:00
styling.nix	waybar: make module a freeform module, remove warnings	2021-11-29 20:52:06 -05:00
systemd-with-graphical-session-target.nix	waybar: fix command not found when reloading (#2865)	2022-04-16 18:31:03 -04:00
systemd-with-graphical-session-target.service	waybar: fix service After value	2023-09-19 21:39:16 +02:00