Timo
bed974bd4d
The previous fix listed both profiles' primaries, "output": ["eDP-1",
"DP-1"] -- but DP-1 is the laptop's second monitor too, so the laptop
would have got a bar on it as well as on eDP-1. No static list can express
"the main monitor" when the two machines share an output name.
Resolve it at launch instead. hypr/scripts/bar asks Hyprland for the
monitor at position 0x0 -- the main monitor in both profiles -- writes
{"output": "<name>"} to ~/.cache/waybar-output.jsonc, and execs waybar;
waybar/config.jsonc includes that fragment. autostart/services, the
bar_reload bind and the performance script all go through the wrapper, so
a reload re-resolves after docking. Signals still target the waybar
process, not the wrapper.
Verified all three paths on mainPC: the fragment pins the bar to DP-1
only, an empty fragment falls back to a bar on every output, and a
fragment naming a disconnected output maps nothing (the failure mode this
started from). Config parses on both profiles.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01StGBghPW9Dm7z7uj2VNWHr
21 lines
485 B
JSON
21 lines
485 B
JSON
[
|
|
{
|
|
"include": [
|
|
"~/.config/waybar/bars/main.jsonc",
|
|
// "output", resolved per machine by hypr/scripts/bar -- see the comment
|
|
// there. Missing file just means a bar on every monitor.
|
|
"~/.cache/waybar-output.jsonc",
|
|
],
|
|
"height": 50,
|
|
"layer": "top",
|
|
"mode": "dock",
|
|
"exclusive": true,
|
|
"passtrough": false,
|
|
"gtk-layer-shell": true,
|
|
"margin-top": 5,
|
|
"margin-left": 5,
|
|
"margin-bottom": 0,
|
|
"margin-right": 5,
|
|
},
|
|
]
|