omarchy-shell: a per-device input panel for scroll direction, scroll speed and pointer tuning

[martin-irwin]

The gap

Scroll direction, scroll speed and pointer tuning are all configurable per input device today — but only by hand-editing ~/.config/hypr/input.lua. There's no UI for any of it, which makes them invisible to most users. Inverting scroll on one external mouse currently means knowing that hl.device exists, knowing the device's Hyprland name, and knowing not to reach for the global input.natural_scroll (which would drag the touchpad and trackpoint along with it).

An input section in the shell — pick a device, flip scroll direction, drag a scroll-speed slider — would surface settings that already work.

It's all already supported per-device

Probing the hl.device field validator (Omarchy 4.0.0-1, Hyprland Lua parser):

Field
natural_scroll	✅ scroll direction
scroll_factor	✅ scroll speed
sensitivity	✅ pointer speed
accel_profile	✅ flat / adaptive
left_handed	✅
middle_button_emulation	✅

So this is a UI over an existing, validated config surface — not new compositor plumbing. Device names come straight from hyprctl devices (logitech-mx-master-3s, elan-touchpad, elan-trackpoint), which also gives the panel its device list for free.

Persistence: the mechanism already exists

The obvious objection is that a widget would have to write to ~/.config/hypr/input.lua, a hand-edited, comment-bearing user file — and that hyprctl keyword is no longer available under the Lua parser (keyword can't work with non-legacy parsers. Use eval.), while hyprctl eval doesn't survive a reload.

But Omarchy already has a generated-Lua-state channel for exactly this:

-- default/hypr/toggles.lua
local toggles_dir = paths.state_home .. "/omarchy/toggles/hypr"
package.path = toggles_dir .. "/?.lua;" .. package.path
require_all.files(toggles_dir, nil, { reload = true })

~/.local/state/omarchy/toggles/hypr/ already holds machine-written flags.lua and internal-monitor-clamshell.lua, and bootstrap.lua puts ~/.local/state on package.path ahead of ~/.config for precisely this reason. A settings panel could write input-devices.lua there and have it applied on reload, with the user's own input.lua never touched and hand-written overrides still winning if they want them.

Sketch

• Device list from hyprctl devices, grouped mice / touchpads / keyboards
• Per device: natural scroll toggle, scroll speed slider, pointer speed slider, accel profile
• Writes ~/.local/state/omarchy/toggles/hypr/input-devices.lua, then reloads

Explicitly out of scope

Button remapping. button_map is not a valid hl.device field, and remapping an MX Master's thumb buttons is HID++ work — solaar / libratbag+piper (repos) or logiops (AUR), not the compositor. Worth its own thread; folding it in here would turn a small UI addition into a device-daemon integration.

Prior art

#7033 proposes folding NetworkManager VPN profiles into the Quattro Network panel — same shape of idea: surface existing capability in a panel that's already there.