diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-06 17:36:32 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-06 17:36:32 -0500 |
| commit | 955d02333a75d08ede6c96ac0c1efe5a81077693 (patch) | |
| tree | cb4063552131e95b2b8931140bd0bdcb32fbc4f7 /archsetup.conf.example | |
| parent | 8494ea281c2cbfc2f2216cd3c9293a9ccdec0641 (diff) | |
| download | archsetup-955d02333a75d08ede6c96ac0c1efe5a81077693.tar.gz archsetup-955d02333a75d08ede6c96ac0c1efe5a81077693.zip | |
fix(hyprland): override nogroup_border so scratchpads aren't magenta
Pyprland 3.4 started applying a `group deny` windowrule to every scratchpad. In Hyprland that flag routes the border through `col.nogroup_border` and `col.nogroup_border_active` instead of the regular `col.*_border` colors. Hyprland's defaults for those two are pink and bright magenta, so every scratchpad came up with a glaring magenta frame after the 3.4 upgrade.
I set `col.nogroup_border_active` to dupre blue (#67809c) and `col.nogroup_border` to the same dark grey the inactive border already uses. Focused scratchpads read as a deliberate accent, unfocused ones blend in. The two new lines sit next to the existing `col.*_border` entries with a comment naming the cause, so the next person reading this config doesn't have to re-derive it.
Diffstat (limited to 'archsetup.conf.example')
0 files changed, 0 insertions, 0 deletions
