Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-3932GitHub issuePublicReceived

Setting default editor to "fresh" does not work

Reported by jessecrouch · filed Dec 29, 2025Closed upstream on 2026-01-07 by commit 7c213db46dba (closed by dhh). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Setting default editor to "fresh" does not workrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Omarchy 3.2.x (current)

What's wrong?

Setting EDITOR=fresh in ~/.config/uwsm/default does not work when using the Omarchy menu to edit config files. The toast notification appears briefly but the editor never opens.

This is because omarchy-launch-editor has a hardcoded list of known TUI editors:

case "$EDITOR" in
nvim | vim | nano | micro | hx | helix)
  exec omarchy-launch-tui "$EDITOR" "$@"
  ;;
*)
  exec setsid uwsm-app -- "$EDITOR" "$@"
  ;;
esac

Since fresh is not in the list, it falls through to the GUI editor path which silently fails.

Proposed fix

Add fresh to the list of recognized TUI editors, similar to how helix was added in #1740.

Suggestion for future improvement

Rather than maintaining a hardcoded allowlist of TUI editors, consider:
- A user-configurable list (e.g., OMARCHY_TUI_EDITORS env var)
- Inverting the logic to have a list of known GUI editors instead (smaller list)
- Auto-detection of whether a command requires a TTY

This would prevent similar issues for users of other terminal editors.

View raw text
### System details

Omarchy 3.2.x (current)

### What's wrong?

Setting `EDITOR=fresh` in `~/.config/uwsm/default` does not work when using the Omarchy menu to edit config files. The toast notification appears briefly but the editor never opens.

This is because `omarchy-launch-editor` has a hardcoded list of known TUI editors:

```bash
case "$EDITOR" in
nvim | vim | nano | micro | hx | helix)
  exec omarchy-launch-tui "$EDITOR" "$@"
  ;;
*)
  exec setsid uwsm-app -- "$EDITOR" "$@"
  ;;
esac
```

Since `fresh` is not in the list, it falls through to the GUI editor path which silently fails.

### Proposed fix

Add `fresh` to the list of recognized TUI editors, similar to how `helix` was added in #1740.

### Suggestion for future improvement

Rather than maintaining a hardcoded allowlist of TUI editors, consider:
- A user-configurable list (e.g., `OMARCHY_TUI_EDITORS` env var)
- Inverting the logic to have a list of known GUI editors instead (smaller list)
- Auto-detection of whether a command requires a TTY

This would prevent similar issues for users of other terminal editors.

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.