OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
hyprland-config low occasional DISPUTE

Fix SUPER+mouse window drag needing two presses after typing

hyprlandarchomarchy
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The symptom and the fix's effect hold, but the cause is wrong for 0.56.2. hlBind in Hyprland v0.56.2 LuaBindingsToplevel.cpp reads click and drag (each sets kb.release = true) and never reads a mouse field, so kb.mouse is never set from Lua. On this workstation, hyprctl binds -j (read-only) shows Omarchy's own SUPER + mouse:272 bind with "mouse": false although tiling.lua passes { mouse = true }. Issue 15700 reports both halves: mouse is silently ignored, and drag = true swallows the first press. The issue was closed by the bot without a fix. window.drag() works because the dispatcher itself runs the mouse movewindow action, and what breaks it is the release latch that drag adds. The commands stay valid because { mouse = true } is harmless and matches the wiki, but the cause and the explanation are rewritten. Second audit confirmed the corrected text: Second pass over the 2026-10-04 correction, which holds. hlBind in v0.56.2 LuaBindingsToplevel.cpp reads repeating, locked, release, non_consuming, auto_consuming, transparent, ignore_mods, dont_inhibit, long_press, submap_universal, click and drag, and never a mouse field. click and drag each set kb.release = true. dsp_mouseDrag and dsp_mouseResize in LuaBindingsDispatchers.cpp call CA::mouse("movewindow") and CA::mouse("resizewindow ...") themselves, which is why the drag works without the mouse flag. Issue 15700 describes both halves, including the releasePending latch that a keystroke clears, and was closed by the bot without a fix. The bind flags wiki defines drag as firing on release past binds:drag_threshold. On this workstation the read-only hyprctl binds -j query shows Omarchy's SUPER + mouse:272 and mouse:273 binds with release false and mouse false, as the record says, and default/hypr/bindings/tiling.lua lines 70 and 71 bind them with { mouse = true }. The jq check in the fix runs as written. This record already carries audit_status corrected, and this verdict confirms that correction rather than replacing it.

The cause above was rewritten on 2026-10-04 to match this note; the fix was corrected by the audit itself.

Symptom

A mouse-button bind for moving or resizing windows, such as hl.bind("mouse:275", hl.dsp.window.drag(), { drag = true }), ignores the first press after you type anything. The second press starts the drag, and it keeps working until you type again.

Cause

In the Lua bind API, drag = true (and click = true) sets the bind to fire on release, after the pointer moved past binds:drag_threshold. That makes a continuous dispatcher such as window.drag() or window.resize() miss the first press after any keystroke. In Hyprland 0.56.2, hlBind does not parse a mouse field at all, so { mouse = true } is silently ignored and hyprctl binds -j reports "mouse": false even for Omarchy's own SUPER + mouse:272 bind. The drag still works without it, because the window.drag() and window.resize() dispatchers start the mouse action themselves. What fixes the double press is removing drag = true.

Fix

Remove drag = true from drag and resize binds. { mouse = true } is what the wiki and Omarchy's defaults use. Hyprland 0.56.2 ignores it, but it is harmless and keeps the bind correct for releases that parse it.

**Plain Arch**, ~/.config/hypr/hyprland.lua:


hl.bind("SUPER + mouse:272", hl.dsp.window.drag(), { mouse = true })
hl.bind("SUPER + mouse:273", hl.dsp.window.resize(), { mouse = true })
hl.bind("mouse:275", hl.dsp.window.drag(), { mouse = true })

**Omarchy 4.** The defaults in /usr/share/omarchy/default/hypr/bindings/tiling.lua already bind SUPER + left and SUPER + right this way. For extra buttons, add in ~/.config/hypr/bindings.lua:


o.bind("mouse:275", "Move window", hl.dsp.window.drag(), { mouse = true })
o.bind("mouse:276", "Resize window", hl.dsp.window.resize(), { mouse = true })

Check that no drag bind carries the release latch:


hyprctl binds -j | jq -c '.[] | select(.key | startswith("mouse:")) | {modmask, key, release, mouse}'

release must be false for drag and resize binds. On 0.56.2, mouse reads false for every Lua bind and that is expected. Keep drag = true and click = true for actions that should run once on release, such as floating a window on click.

Verify

Type a few characters, then press the bound button once and move: the window follows on the first press.

Sources

lua-mouse-drag-bind-needs-two-presses