Fix: Chase Hyprland 0.53
#1424
So Hyprland will break user configs soon. Please follow the changes in here.
Edit: as mentioned in https://github.com/hyprwm/Hyprland/issues/12274 we will try our best to smooth out any config issues in our part.
should we adopt for this syntax with braces and name
windowrule {
name = apply-something
match:class = my-window
border_size = 10
}
@rubiin We only add name for windows rule that we want to dynamically turn off and on. Which is I think way way better for rules with categories. But do we really need this? ( One usecase is to turn off hyde's windows rules dynamically? Any other use case?
I am treating this as global as of now so names are not important. Have you figured any usecase? or maybe categorize the windowrules ? Let me know
use version guards and save yourself some hassle.
https://wiki.hypr.land/Configuring/Uncommon-tips--tricks/#config-versioning
we love you vaxx 😌
@vaxerski Will this skip parsing/loading the configs when version mismatched?
just a conditional like any other in hyprlang, but yes this is a way to version-gate configs
@vaxerski I am currently testing it. Currently it is not working on hyprland-git? For testing I added this block
This is my full test block and I am using hyprland-git
Hyprland 0.52.0 built from branch main at commit b5a2ef77b7876798d33502f8de006f9c478c12db clean (i18n: add Português (Portugal) translation ( 12328)).
# checking if var is set by hyprland
exec = notify-send "Test: $HYPRLAND_V_0_53"
# hyprlang if HYPRLAND_V_0_53
exec = notify-send "confirmed: $HYPRLAND_V_0_53"
# hyprlang endif
# hyprlang if !HYPRLAND_V_0_53
exec = notify-send "Still the old: config $HYPRLAND_V_0_53"
# hyprlang endif
oopes, fixed in https://github.com/hyprwm/hyprlang/commit/a318deec0c12409ec39c68d2be8096b636dc2a5c