Hyprland version
Hyprland 0.54.0 built from branch v0.54.0 at commit 0002f148c9a4fe421a9d33c0faa5528cdc411e62 clean (version: bump to 0.54.0).
Date: Fri Feb 27 18:03:19 2026
Tag: v0.54.0, commits: 6935
Libraries:
Hyprgraphics: built against 0.5.0, system has unknown
Hyprutils: built against 0.11.0, system has unknown
Hyprcursor: built against 0.1.13, system has unknown
Hyprlang: built against 0.6.8, system has unknown
Aquamarine: built against 0.10.0, system has unknown
Version ABI string: 0002f148c9a4fe421a9d33c0faa5528cdc411e62_aq_0.10_hu_0.11_hg_0.5_hc_0.1_hlg_0.6
no flags were set
Fedora repo - wiki update suggestion
Sidenote:
Finally switched to a recent build of Hyprland on Fedora(0.54 from 0.51). The copr repo recommended by wiki (solopasha) seems to be abandoned, but hermitfeather seems do a good job (thanks).
The transition was pretty smooth so far but I noticed following change in semantics:
Window Rules: window_w / window_h change in semantics when used inside move
When using both size and move inside a windowrule to position a floating window, in 0.51 I was able to use a window_w inside the move expression that referred to the new window size. So I could use expressions like:
move 100%-w-10 100%-h-10 (back then)
move = ((monitor_w-window_w)-10) ((monitor_h-window_h)-10) (in today’s syntax)
to move the window 10px from the bottom right corner, independent of the window size (even when adjusting its size a line before).
But now the window_w / window_h seems to always refer to the initial window size (the size line is not reflected). Even separating the move into a different rule (rule ordering) doesn’t seem to help.
There is of course a workaround: using the value / expression that I used in size directly, but this was (in my opinion) a much cleaner solution & one that could be applied to multiple differently sized widows all at once.
Is there a good reason for this change or is it just an omission?