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-4818GitHub issuePublicReceived

Sublime Text install does not expose sublime_text on PATH, so Defaults → Editor never lists it

Reported by luviathanx · filed Sep 1, 2026Closed upstream on 2026-09-21 by the merge of PR #9656 (closed by bjarneo). GitHub close reason: completed.

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

Sublime Text install does not expose sublime_text on PATH, so Defaults → Editor never lists itrevision 1 · captured 2026-10-04 12:03 UTC via poll

System details

Intel Core i7-7820HQ, Intel HD Graphics 630 + AMD Radeon Pro 455, Apple MacBookPro14,3, Omarchy 4.0.1-1 (x86_64)

What's wrong?

Installing Sublime Text from Install → Editor → Sublime Text succeeds, but the app never appears under Setup → Defaults → Editor. After install that menu still only listed Neovim.

The install path and the defaults path use two different identities, and only one of them matches what sublime-text-4 actually ships.

Install (this part works) in default/omarchy/omarchy-menu.jsonc:

"install.editor.sublime": {
  "action": "omarchy-install-and-launch 'Sublime Text' sublime-text-4 sublime_text"
}

That installs package sublime-text-4 and launches gtk-launch sublime_text, which is correct because the desktop file is sublime_text.desktop.

Defaults (this part fails) in the same file:

"setup.default.editor.sublime": {
  "when": "omarchy-cmd-present sublime_text",
  "checked": "[[ \"$(omarchy-default-editor)\" == \"sublime_text\" ]]",
  "action": "omarchy-default-editor sublime_text"
}

omarchy-cmd-present is command -v. The official package does not put sublime_text on PATH.

On a stock install of sublime-text-4 4.4200-1:

WhatResult
packagesublime-text-4 installed
command -v subl/usr/bin/subl (wrapper: exec /opt/sublime_text/sublime_text "$@")
command -v sublime_textmissing
real binary/opt/sublime_text/sublime_text (not on PATH)
desktop file/usr/share/applications/sublime_text.desktop (Exec=/usr/bin/subl %F)

So omarchy-cmd-present sublime_text fails and the Defaults row is hidden.

Second failure if you force it: omarchy-default-editor stores the name sublime_text, and omarchy-launch-editor then does omarchy-cmd-present "$editor" and falls back to nvim when that command is missing. Selecting Sublime as the default editor would not actually launch it.

Unlike VS Code / Zed / Helix / Emacs, Sublime has no dedicated omarchy-install-editor-* script, so install does not create a sublime_text wrapper either.

Steps to reproduce

  1. Install from Install → Editor → Sublime Text (package sublime-text-4).
  2. Open Setup → Defaults → Editor.
  3. Sublime Text is missing; only editors whose exact command is on PATH appear (Neovim / nvim in this case).
  4. omarchy-cmd-present sublime_text exits 1; omarchy-cmd-present subl exits 0.

Expected

After installing Sublime from the Omarchy menu, it should appear in Defaults → Editor, and choosing it should make omarchy-launch-editor open Sublime.

Suggested fix

Keep sublime_text as the desktop-file id for gtk-launch, but treat subl as the PATH command (or install a sublime_text symlink/wrapper onto PATH as part of the Sublime install). omarchy-default-editor / omarchy-launch-editor need to use a command that actually exists after sublime-text-4 is installed.

Related but distinct: #7810 (setting a GUI default editor does not update XDG MIME defaults).

omarchy-debug --no-sudo --print captured locally at /tmp/omarchy-debug.log (Omarchy 4.0.1-1). Happy to attach it if useful; the mismatch above reproduces from the package file list without extra logs.

View raw text
### System details
Intel Core i7-7820HQ, Intel HD Graphics 630 + AMD Radeon Pro 455, Apple MacBookPro14,3, Omarchy 4.0.1-1 (x86_64)

### What's wrong?

Installing Sublime Text from **Install → Editor → Sublime Text** succeeds, but the app never appears under **Setup → Defaults → Editor**. After install that menu still only listed Neovim.

The install path and the defaults path use two different identities, and only one of them matches what `sublime-text-4` actually ships.

**Install (this part works)** in `default/omarchy/omarchy-menu.jsonc`:

```jsonc
"install.editor.sublime": {
  "action": "omarchy-install-and-launch 'Sublime Text' sublime-text-4 sublime_text"
}
```

That installs package `sublime-text-4` and launches `gtk-launch sublime_text`, which is correct because the desktop file is `sublime_text.desktop`.

**Defaults (this part fails)** in the same file:

```jsonc
"setup.default.editor.sublime": {
  "when": "omarchy-cmd-present sublime_text",
  "checked": "[[ \"$(omarchy-default-editor)\" == \"sublime_text\" ]]",
  "action": "omarchy-default-editor sublime_text"
}
```

`omarchy-cmd-present` is `command -v`. The official package does **not** put `sublime_text` on `PATH`.

On a stock install of `sublime-text-4 4.4200-1`:

| What | Result |
|---|---|
| package | `sublime-text-4` installed |
| `command -v subl` | `/usr/bin/subl` (wrapper: `exec /opt/sublime_text/sublime_text "$@"`) |
| `command -v sublime_text` | missing |
| real binary | `/opt/sublime_text/sublime_text` (not on `PATH`) |
| desktop file | `/usr/share/applications/sublime_text.desktop` (`Exec=/usr/bin/subl %F`) |

So `omarchy-cmd-present sublime_text` fails and the Defaults row is hidden.

**Second failure if you force it:** `omarchy-default-editor` stores the name `sublime_text`, and `omarchy-launch-editor` then does `omarchy-cmd-present "$editor"` and falls back to `nvim` when that command is missing. Selecting Sublime as the default editor would not actually launch it.

Unlike VS Code / Zed / Helix / Emacs, Sublime has no dedicated `omarchy-install-editor-*` script, so install does not create a `sublime_text` wrapper either.

### Steps to reproduce

1. Install from **Install → Editor → Sublime Text** (package `sublime-text-4`).
2. Open **Setup → Defaults → Editor**.
3. Sublime Text is missing; only editors whose exact command is on `PATH` appear (Neovim / `nvim` in this case).
4. `omarchy-cmd-present sublime_text` exits 1; `omarchy-cmd-present subl` exits 0.

### Expected

After installing Sublime from the Omarchy menu, it should appear in Defaults → Editor, and choosing it should make `omarchy-launch-editor` open Sublime.

### Suggested fix

Keep `sublime_text` as the desktop-file id for `gtk-launch`, but treat `subl` as the PATH command (or install a `sublime_text` symlink/wrapper onto `PATH` as part of the Sublime install). `omarchy-default-editor` / `omarchy-launch-editor` need to use a command that actually exists after `sublime-text-4` is installed.

Related but distinct: #7810 (setting a GUI default editor does not update XDG MIME defaults).

`omarchy-debug --no-sudo --print` captured locally at `/tmp/omarchy-debug.log` (Omarchy 4.0.1-1). Happy to attach it if useful; the mismatch above reproduces from the package file list without extra logs.

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.