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.
omarchy-menu support using $EDITOR / $VISUAL instead of hardcoding nvim
Reported by logannc · filed Aug 10, 2025Closed upstream on 2025-08-31 by dhh, as a duplicate of #503 (R-2417). GitHub close reason: duplicate.
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
I thought this would be almost as simple as replacing nvim with $EDITOR in edit_in_nvim in omarchy-menu (and changing the function name), but it appears $EDITOR is unset in that context. It is also unset when I set it in .profile... not sure why we don't have our exported env vars in this scope.
Another minor complication is the prefix of alacritty -e flashes a window if you use $EDITOR=code or something like that, so might need different calling conventions for $VISUAL and $EDITOR. Call $VISUAL "$1" directly and alacritty -e $EDITOR "$1"?
View raw text
I thought this would be almost as simple as replacing `nvim` with `$EDITOR` in `edit_in_nvim` in `omarchy-menu` (and changing the function name), but it appears `$EDITOR` is unset in that context. It is also unset when I set it in `.profile`... not sure why we don't have our exported env vars in this scope. Another minor complication is the prefix of `alacritty -e` flashes a window if you use `$EDITOR=code` or something like that, so might need different calling conventions for `$VISUAL` and `$EDITOR`. Call `$VISUAL "$1"` directly and `alacritty -e $EDITOR "$1"`?
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.