Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Use $mainMod instead of SUPER for keybinds
Reported by kromsam · filed Aug 26, 2025Closed upstream on 2025-08-31 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Currently, SUPER as modkey is pretty much hard-coded throughout the omarchy defaults.
The standard Hyprland config does this differently:
$mainMod = SUPER # Sets "Windows" key as main modifier
and thenbind = $mainMod, Q, exec, $terminal
Would it make sense to add this modkey variable to the bindings, such that users can change their modkey a bit easier?
I thought that we could do this by adding an extra source to hyprland.conf: mod.conf that contains the line from the hyprland config. I tried configuring this myself for a bit, but I got a bit stuck. Would it be even possible?
(FYI: Im currently writing from a Superless IBM Model M - keyboard ;) , that's why this came up. I would like to set it to CAPSLOCK)
View raw text
Currently, SUPER as modkey is pretty much hard-coded throughout the omarchy defaults. The standard Hyprland config does this differently: https://github.com/hyprwm/Hyprland/blob/0ed880f3f7dc2c746bf3590eee266c010d737558/example/hyprland.conf#L224 `$mainMod = SUPER # Sets "Windows" key as main modifier` and then `bind = $mainMod, Q, exec, $terminal` Would it make sense to add this modkey variable to the bindings, such that users can change their modkey a bit easier? I thought that we could do this by adding an extra source to hyprland.conf: `mod.conf` that contains the line from the hyprland config. I tried configuring this myself for a bit, but I got a bit stuck. Would it be even possible? (FYI: Im currently writing from a Superless IBM Model M - keyboard ;) , that's why this came up. I would like to set it to CAPSLOCK)
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.