From c1dc60af0016bd14c1e72e8c2ec670efd3b1e9d2 Mon Sep 17 00:00:00 2001 From: Hermenix Date: Sat, 3 Oct 2026 11:50:52 +0000 Subject: [PATCH] hyprland-conf: follow the pointer, because one now exists vm-pointer measured what this setting actually does: with follow_mouse=0 Hyprland delivers pointer events only to the keyboard-focused window, so a click aimed at 0.25,0.75 of a session's container put the cursor at x=299 y=519 -- inside that window -- and both clients reported nothing. The click was aimed correctly and delivered nowhere. The comment here said 'no pointer will ever exist; do not let focus depend on one', which was true when written and is false now that the broker injects a virtual pointer. The cursor lease already serialises input, so focus following the pointer cannot make two sessions fight over the keyboard. --- nix/hyprland-conf.nix | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/nix/hyprland-conf.nix b/nix/hyprland-conf.nix index 9ffe62e..6bc0a1a 100644 --- a/nix/hyprland-conf.nix +++ b/nix/hyprland-conf.nix @@ -79,8 +79,18 @@ in '' } input { - # No pointer will ever exist; do not let focus depend on one. - follow_mouse = 0 + # Focus follows the pointer. This was `0`, on the reasoning written here + # that no pointer would ever exist — true when it was written, and false + # now that the broker injects one. + # + # It is not a preference. With `0` Hyprland delivers pointer events only to + # the keyboard-focused window: measured in `vm-pointer`, a click aimed at + # 0.25,0.75 of a session's container placed the cursor at x=299 y=519, + # inside that window, and **both** clients reported nothing — the click was + # aimed correctly and delivered nowhere. The cursor lease already + # serialises input, so letting the pointer move keyboard focus cannot make + # two sessions fight over the keyboard. + follow_mouse = 1 } # Frames cost capture bandwidth and CPU, and no one is watching the easing.