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

Stop SUPER+J throwing 'no such layoutmsg for scrolling'

omarchyhyprland
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The SUPER + J bind is hl.dsp.layout("togglesplit") with no condition, at tiling.lua:4 on 4.0.4-1 and tiling.lua:5 on quattro. Issue #7556 is open, and its consolidation comment lists the duplicates and five unmerged PRs. #9726 was closed as a duplicate of it. ScrollingAlgorithm.cpp at v0.56.2 returns no such layoutmsg for scrolling for anything it does not handle, and it accepts consume_or_expel with a next or prev argument. The Lua API exists in v0.56.2 as the fix uses it: hl.get_active_workspace and hl.get_active_special_workspace in LuaBindingsQuery.cpp, the tiled_layout field in LuaWorkspace.cpp, and hl.dispatch. hyprctl activeworkspace -j here reports tiledLayout: "dwindle", so the layout names match. o.bind passes a function through to hl.bind, as Omarchy's own SUPER+CTRL+Z bind does. The bind was not replaced live.

Symptom

Pressing SUPER+J (Toggle window split) shows a red notification: Runtime error in lua: ?:?: no such layoutmsg for scrolling (also seen as error: =[C]:-1: no such layoutmsg for scrolling). It happens only on some workspaces, the ones you switched with SUPER+L.

Cause

Omarchy's default SUPER + J in /usr/share/omarchy/default/hypr/bindings/tiling.lua always sends hl.dsp.layout("togglesplit"). togglesplit is a dwindle layout message. SUPER+L (omarchy-hyprland-workspace-layout-toggle) can put any workspace on the scrolling layout, which rejects that message, and Hyprland surfaces the dispatcher error as a Lua runtime error. Still unconditional in 4.0.4-1 and on the quattro branch, with several unmerged PRs proposing different behaviours.

Fix

**Omarchy 4.** Replace the bind in ~/.config/hypr/bindings.lua with one that checks the layout first:


hl.unbind("SUPER + J")
o.bind("SUPER + J", "Toggle window split", function()
  local ws = hl.get_active_special_workspace() or hl.get_active_workspace()
  if ws and ws.tiled_layout == "dwindle" then
    hl.dispatch(hl.dsp.layout("togglesplit"))
  elseif ws and ws.tiled_layout == "scrolling" then
    -- optional: a column action on scrolling, or delete this branch for a no-op
    hl.dispatch(hl.dsp.layout("consume_or_expel next"))
  end
end)

The function form matters: a dispatcher passed directly is built once at load time, so the layout check would never run per keypress.

**Plain Arch.** Same shape in your own config if you bind togglesplit and use per-workspace layouts.

Verify

On a scrolling workspace (hyprctl activeworkspace -j | jq .tiledLayout prints "scrolling"), SUPER+J produces no error notification. On a dwindle workspace it still toggles the split.

Sources

super-j-togglesplit-error-on-scrolling-layout