Replies: 2 comments 1 reply
|
Yes please. I come from xmonad and I find the default behavior very annoying. Thanks for the workaround @ecleel ! Adding the following to |
|
Opened #9780 for this. Note that Omarchy 4 moved these bindings from o.bind("SUPER + " .. key, "Switch to workspace " .. workspace,
hl.dsp.focus({ workspace = tostring(workspace), on_current_monitor = true }))Same native Hyprland dispatcher underneath, so the proposal stands as written — it is a one-line change in Verified on a dual-monitor setup: dispatching from the second screen at a workspace living on the first, the plain focus jumps focus to the other monitor, while For anyone landing here who wants it today without waiting on the PR, the Omarchy 4 version of the workaround in for workspace = 1, 10 do
local key = "SUPER + code:" .. tostring(workspace + 9)
hl.unbind(key)
o.bind(key, "Switch to workspace " .. workspace, hl.dsp.focus({ workspace = tostring(workspace), on_current_monitor = true }))
end(That covers 1-10; my original snippet above stopped at Thanks again @ecleel for digging out the dispatcher in the first place. |
Uh oh!
There was an error while loading. Please reload this page.
Problem
With the current default bindings in
default/hypr/bindings/tiling-v2.conf:bindd = SUPER, code:10, Switch to workspace 1, workspace, 1
...
the
workspace, Ndispatcher follows the workspace to whichever monitor italready lives on. On a dual-monitor setup, pressing
SUPER+1while focusedon the external screen silently jumps focus to the laptop — the external
screen appears to "do nothing," which is confusing, especially for users
coming from macOS (Omarchy's stated audience).
This has come up before:
split-monitor-workspacespluginProposal
Replace the 10
workspace, Ndefaults withfocusworkspaceoncurrentmonitor, N,a native Hyprland dispatcher (added in 0.41.0) that brings the target
workspace to the currently focused monitor.
All reactions