1
0
Fork 0
mirror of https://github.com/nix-community/home-manager synced 2024-11-27 13:39:46 +01:00
home-manager/tests/modules/programs/waybar/settings-complex-expected.json
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

62 lines
1 KiB
JSON

[
{
"custom/my-module": {
"exec": "@dummy@/bin/dummy",
"format": "hello from {}"
},
"height": 30,
"idle_inhibitor": {
"format": "{icon}"
},
"layer": "top",
"modules-center": [
"sway/window"
],
"modules-left": [
"sway/workspaces",
"sway/mode",
"custom/my-module"
],
"modules-right": [
"idle_inhibitor",
"pulseaudio",
"network",
"cpu",
"memory",
"backlight",
"tray",
"battery#bat1",
"battery#bat2",
"clock"
],
"output": [
"DP-1"
],
"position": "top",
"sway/mode": {
"tooltip": false
},
"sway/window": {
"max-length": 120
},
"sway/workspaces": {
"all-outputs": true,
"disable-scroll": true
}
},
{
"modules-center": [
"clock"
],
"modules-left": [
"sway/mode"
],
"output": [
"!DP-1"
],
"position": "bottom",
"sway/mode": {
"tooltip": true
}
}
]