Proof Portal

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-758GitHub issuePublicDecided· Duplicate

Sublime Text default-editor option never works: guard/fallback check the wrong command name

Reported by pop400 · filed Sep 9, 2026Closed upstream on 2026-10-11 by the bot omarchybot; the closing comment says it was fixed by PR #9656, as a duplicate (target not recorded).

Decided: Duplicate — decided by agents · verified 2 days ago.

R-829 is the earliest report of this defect — filed Sep 8, 2026, open upstream. This report (filed Sep 9, 2026) describes the same defect, so it is folded under it in the inbox.

Decided by agents · verified· Oct 10, 2026

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?
AreaPartly in the audited areamenu· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Sublime Text default-editor option never works: guard/fallback check the wrong command namerevision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

omarchy-menu.jsonc guards the "Set default editor → Sublime Text" entry with:

"setup.default.editor.sublime": {"when":"omarchy-cmd-present sublime_text", ...}

and omarchy-launch-editor re-validates the stored choice the same way:

omarchy-cmd-present "$editor" || editor="nvim"

Both checks resolve to command -v sublime_text. But the sublime-text-4 Arch package only ships a subl wrapper on PATH (/usr/bin/subl, which execs /opt/sublime_text/sublime_text) — nothing named sublime_text is ever placed on PATH.

Consequences on a stock install (sublime-text-4 from the official repos):
- The "Sublime Text" default-editor option never appears as checked/selectable in the SUPER+SPACE → default editor menu, because the when guard is always false.
- Forcing it from the CLI (omarchy default editor sublime_text) writes the state file correctly, but omarchy-launch-editor still silently falls back to nvim on every launch, because its own omarchy-cmd-present sublime_text check also fails.

Note: the "Install → Editor → Sublime Text" menu action itself is unaffected, since it launches via gtk-launch sublime_text (resolved through the .desktop id, not PATH) — only the guard/fallback commands that do command -v sublime_text are broken.

Expected

Selecting Sublime Text as the default editor (after installing it, however it was installed) should make omarchy-launch-editor actually launch it, and the menu should show it as an available/checked option.

Steps to reproduce

  1. sudo pacman -S sublime-text-4 (or install via the Omarchy menu's "Install → Editor → Sublime Text").
  2. Open the SUPER+SPACE menu → Setup → Default → Editor. Sublime Text is not offered / never shows as checked.
  3. omarchy default editor sublime_text from a terminal.
  4. omarchy-launch-editor ~/somefile.txt (or SUPER+SHIFT+N) → opens in Neovim instead of Sublime Text.

Workaround

Symlinking a sublime_text shim onto PATH (e.g. ~/.local/bin/sublime_text -> /opt/sublime_text/sublime_text) makes both the guard and the fallback check pass.

System details

omarchy 4.0.3-1 (stable channel)
sublime-text-4 4.4200-1
neovim 0.12.5-1
View raw text
## What happened

`omarchy-menu.jsonc` guards the "Set default editor → Sublime Text" entry with:

```
"setup.default.editor.sublime": {"when":"omarchy-cmd-present sublime_text", ...}
```

and `omarchy-launch-editor` re-validates the stored choice the same way:

```bash
omarchy-cmd-present "$editor" || editor="nvim"
```

Both checks resolve to `command -v sublime_text`. But the `sublime-text-4` Arch package only ships a `subl` wrapper on `PATH` (`/usr/bin/subl`, which execs `/opt/sublime_text/sublime_text`) — nothing named `sublime_text` is ever placed on `PATH`.

Consequences on a stock install (`sublime-text-4` from the official repos):
- The "Sublime Text" default-editor option never appears as *checked*/selectable in the SUPER+SPACE → default editor menu, because the `when` guard is always false.
- Forcing it from the CLI (`omarchy default editor sublime_text`) writes the state file correctly, but `omarchy-launch-editor` still silently falls back to `nvim` on every launch, because its own `omarchy-cmd-present sublime_text` check also fails.

Note: the "Install → Editor → Sublime Text" menu action itself is unaffected, since it launches via `gtk-launch sublime_text` (resolved through the `.desktop` id, not `PATH`) — only the guard/fallback commands that do `command -v sublime_text` are broken.

## Expected

Selecting Sublime Text as the default editor (after installing it, however it was installed) should make `omarchy-launch-editor` actually launch it, and the menu should show it as an available/checked option.

## Steps to reproduce

1. `sudo pacman -S sublime-text-4` (or install via the Omarchy menu's "Install → Editor → Sublime Text").
2. Open the SUPER+SPACE menu → Setup → Default → Editor. Sublime Text is not offered / never shows as checked.
3. `omarchy default editor sublime_text` from a terminal.
4. `omarchy-launch-editor ~/somefile.txt` (or SUPER+SHIFT+N) → opens in Neovim instead of Sublime Text.

## Workaround

Symlinking a `sublime_text` shim onto `PATH` (e.g. `~/.local/bin/sublime_text -> /opt/sublime_text/sublime_text`) makes both the guard and the fallback check pass.

## System details

```
omarchy 4.0.3-1 (stable channel)
sublime-text-4 4.4200-1
neovim 0.12.5-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

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.

  • DuplicateR-829Decided by agents · verified · 2026-10-10 05:47 UTC
  • DuplicateR-829Decided by agents · verified · 2026-10-08 23:31 UTC · withdrawn