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.
Add a couple of special workspace examples
Reported by dimus · filed Oct 18, 2025Closed upstream on 2026-02-01. 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
What do you need?
Special Workspaces are super useful in hyprland. They can be configured to toggle visibility of their windows so they appear/dissappear on demand. While hiding they continue to run in the background, keeping the state intact. It would be great to show a couple of them in the hypr config so people know they exist and can understand their use. For example here is a scratch terminal and a 'calculator' (rather irb playground)
## TERMINAL
workspace = special:termspace, on-created-empty:alacritty --class ala-term
windowrule = float, class:^(ala-term)$
windowrule = pseudo, class:^(ala-term)$
windowrule = size 80% 80%, class:^(ala-term)$
# x y (x horisonal, y vertical from top)
windowrule = center, class:^(ala-term)$
## CALCULATOR
workspace = special:calcspace, on-created-empty:alacritty --class ala-calc -e $HOME/.rbenv/shims/irb
windowrule = float, class:^(ala-calc)$
windowrule = pseudo, class:^(ala-calc)$
windowrule = size 40% 20%, class:^(ala-calc)$
# x y (x horisonal, y vertical from top)
windowrule = move 2% 40%, class:^(ala-calc)$and the corresponding binding would be something like
bind = SUPER, Z, togglespecialworkspace, calcspace
bind = SUPER, T, togglespecialworkspace, termspace View raw text
### What do you need? Special Workspaces are super useful in hyprland. They can be configured to toggle visibility of their windows so they appear/dissappear on demand. While hiding they continue to run in the background, keeping the state intact. It would be great to show a couple of them in the hypr config so people know they exist and can understand their use. For example here is a scratch terminal and a 'calculator' (rather irb playground) ``` ## TERMINAL workspace = special:termspace, on-created-empty:alacritty --class ala-term windowrule = float, class:^(ala-term)$ windowrule = pseudo, class:^(ala-term)$ windowrule = size 80% 80%, class:^(ala-term)$ # x y (x horisonal, y vertical from top) windowrule = center, class:^(ala-term)$ ## CALCULATOR workspace = special:calcspace, on-created-empty:alacritty --class ala-calc -e $HOME/.rbenv/shims/irb windowrule = float, class:^(ala-calc)$ windowrule = pseudo, class:^(ala-calc)$ windowrule = size 40% 20%, class:^(ala-calc)$ # x y (x horisonal, y vertical from top) windowrule = move 2% 40%, class:^(ala-calc)$ ``` and the corresponding binding would be something like ``` bind = SUPER, Z, togglespecialworkspace, calcspace bind = SUPER, T, togglespecialworkspace, termspace ```
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.