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

Sublime Text default editor never works: Omarchy expects a 'sublime_text' command but the package only ships 'subl'

Reported by laodzuh · filed Sep 21, 2026 · open at source

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 21, 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 never works: Omarchy expects a 'sublime_text' command but the package only ships 'subl'revision 1 · captured 2026-09-28 21:23 UTC via poll

Description

Selecting Sublime Text as the default editor never takes effect: omarchy-launch-editor silently falls back to Neovim, and the "Sublime Text" entry under Setup > Default Editor is hidden entirely. I like Sublime Text because I am not very smart and it doesn't give me more than I can handle.

Every Sublime code path in Omarchy assumes a command named sublime_text exists on PATH:

  • omarchy-default-editor writes sublime_text to ~/.local/state/omarchy/defaults/editor
  • omarchy-launch-editor runs omarchy-cmd-present "$editor" || editor="nvim"
  • omarchy-menu.jsonc setup.default.editor.sublime has "when": "omarchy-cmd-present sublime_text"
  • omarchy-menu.jsonc install.editor.sublime runs omarchy-install-and-launch 'Sublime Text' sublime-text-4 sublime_text

But the sublime-text-4 package from the [omarchy] repo (4.4200-1) only installs /usr/bin/subl:

$ pacman -Ql sublime-text-4 | grep /usr/bin/
sublime-text-4 /usr/bin/
sublime-text-4 /usr/bin/subl
$ command -v sublime_text; echo $?
1

So omarchy-cmd-present sublime_text always fails, omarchy-launch-editor falls back to nvim, the menu entry is filtered out, and the post-install launch in omarchy-install-and-launch also fails to start Sublime.

Steps to reproduce

  1. Install Sublime via Install > Editor > Sublime Text (or omarchy pkg add sublime-text-4)
  2. Run omarchy default editor sublime_text (the menu entry isn't visible, so the CLI is the only route)
  3. Press Super+Shift+N, or open Setup > Config > Keybindings

Expected: Sublime Text opens.
Actual: Neovim opens. omarchy default editor still prints sublime_text.

Workaround

printf '#!/bin/bash\nexec subl "$@"\n' > ~/.local/bin/sublime_text && chmod +x ~/.local/bin/sublime_text

Suggested fix

Use subl as the Sublime command in omarchy-default-editor, omarchy-menu.jsonc (both the when check and the install launch arg), or have the sublime-text-4 package ship a sublime_text symlink. Note the sublime_text name is still correct for the Hyprland window rule in default/hypr/apps/system.lua, since that matches the window class, not the binary.

System

  • Omarchy 4.0.4-1
  • sublime-text-4 4.4200-1 (from the [omarchy] repo)
  • CPU: Intel Core i7-7700, GPU: NVIDIA GeForce GTX 1070
View raw text
## Description

Selecting Sublime Text as the default editor never takes effect: `omarchy-launch-editor` silently falls back to Neovim, and the "Sublime Text" entry under Setup > Default Editor is hidden entirely. I like Sublime Text because I am not very smart and it doesn't give me more than I can handle.

Every Sublime code path in Omarchy assumes a command named `sublime_text` exists on `PATH`:

- `omarchy-default-editor` writes `sublime_text` to `~/.local/state/omarchy/defaults/editor`
- `omarchy-launch-editor` runs `omarchy-cmd-present "$editor" || editor="nvim"`
- `omarchy-menu.jsonc` `setup.default.editor.sublime` has `"when": "omarchy-cmd-present sublime_text"`
- `omarchy-menu.jsonc` `install.editor.sublime` runs `omarchy-install-and-launch 'Sublime Text' sublime-text-4 sublime_text`

But the `sublime-text-4` package from the `[omarchy]` repo (4.4200-1) only installs `/usr/bin/subl`:

```
$ pacman -Ql sublime-text-4 | grep /usr/bin/
sublime-text-4 /usr/bin/
sublime-text-4 /usr/bin/subl
$ command -v sublime_text; echo $?
1
```

So `omarchy-cmd-present sublime_text` always fails, `omarchy-launch-editor` falls back to `nvim`, the menu entry is filtered out, and the post-install launch in `omarchy-install-and-launch` also fails to start Sublime.

## Steps to reproduce

1. Install Sublime via Install > Editor > Sublime Text (or `omarchy pkg add sublime-text-4`)
2. Run `omarchy default editor sublime_text` (the menu entry isn't visible, so the CLI is the only route)
3. Press Super+Shift+N, or open Setup > Config > Keybindings

**Expected:** Sublime Text opens.
**Actual:** Neovim opens. `omarchy default editor` still prints `sublime_text`.

## Workaround

```
printf '#!/bin/bash\nexec subl "$@"\n' > ~/.local/bin/sublime_text && chmod +x ~/.local/bin/sublime_text
```

## Suggested fix

Use `subl` as the Sublime command in `omarchy-default-editor`, `omarchy-menu.jsonc` (both the `when` check and the install launch arg), or have the `sublime-text-4` package ship a `sublime_text` symlink. Note the `sublime_text` name is still correct for the Hyprland window rule in `default/hypr/apps/system.lua`, since that matches the window class, not the binary.

## System

- Omarchy 4.0.4-1
- sublime-text-4 4.4200-1 (from the `[omarchy]` repo)
- CPU: Intel Core i7-7700, GPU: NVIDIA GeForce GTX 1070

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:49 UTC
  • DuplicateR-829Decided by agents · verified · 2026-10-09 09:08 UTC · withdrawn