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

Default-editor setting has no effect on file-manager/XDG MIME default (still opens Neovim)

Reported by pop400 · filed Sep 9, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #7299 (R-1714). 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

Default-editor setting has no effect on file-manager/XDG MIME default (still opens Neovim)revision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

Omarchy's "default editor" concept (omarchy default editor <name>, and the SUPER+SPACE → Setup → Default → Editor menu) only feeds omarchy-launch-editor — i.e. things like SUPER+SHIFT+N and any script that calls that binary.

It has no effect on the XDG MIME default-application associations that GTK apps (Nautilus, "Open With", double-click, etc.) actually use. Those come from /usr/share/applications/mimeapps.list, which Omarchy ships with text/plain, application/x-shellscript, text/x-c, application/xml, etc. hard-mapped to nvim.desktop.

So a user can set Sublime Text (or VSCode, Zed, ...) as their "default editor" in the Omarchy menu, see it show as checked/selected there, and still have every text file open in Neovim when opened from the file manager — with no indication anywhere that a second, separate default-app system exists and wasn't touched.

Expected

At minimum, the menu/docs should make clear that "default editor" only controls Omarchy's own launcher shortcuts, not the desktop-wide file-open association. Ideally, setting a default editor through Omarchy would also update the relevant XDG MIME associations (via xdg-mime default <id>.desktop <mimetype>...) so the two stay in sync.

Steps to reproduce

  1. Install e.g. Sublime Text and set it as the Omarchy default editor (menu shows it as checked).
  2. Open Nautilus, double-click any .txt file (or run xdg-mime query default text/plain).
  3. It opens in Neovim (nvim.desktop), not the configured default editor.

System details

omarchy 4.0.3-1 (stable channel)
nautilus 50.3.1-1

~/.config/mimeapps.list has no user override by default, so the system-wide /usr/share/applications/mimeapps.list (owned by the omarchy package) wins, pointing text/plain and related types at nvim.desktop regardless of the configured default editor.

View raw text
## What happened

Omarchy's "default editor" concept (`omarchy default editor <name>`, and the SUPER+SPACE → Setup → Default → Editor menu) only feeds `omarchy-launch-editor` — i.e. things like SUPER+SHIFT+N and any script that calls that binary.

It has no effect on the XDG MIME default-application associations that GTK apps (Nautilus, "Open With", double-click, etc.) actually use. Those come from `/usr/share/applications/mimeapps.list`, which Omarchy ships with `text/plain`, `application/x-shellscript`, `text/x-c`, `application/xml`, etc. hard-mapped to `nvim.desktop`.

So a user can set Sublime Text (or VSCode, Zed, ...) as their "default editor" in the Omarchy menu, see it show as checked/selected there, and still have every text file open in Neovim when opened from the file manager — with no indication anywhere that a second, separate default-app system exists and wasn't touched.

## Expected

At minimum, the menu/docs should make clear that "default editor" only controls Omarchy's own launcher shortcuts, not the desktop-wide file-open association. Ideally, setting a default editor through Omarchy would also update the relevant XDG MIME associations (via `xdg-mime default <id>.desktop <mimetype>...`) so the two stay in sync.

## Steps to reproduce

1. Install e.g. Sublime Text and set it as the Omarchy default editor (menu shows it as checked).
2. Open Nautilus, double-click any `.txt` file (or run `xdg-mime query default text/plain`).
3. It opens in Neovim (`nvim.desktop`), not the configured default editor.

## System details

```
omarchy 4.0.3-1 (stable channel)
nautilus 50.3.1-1
```

`~/.config/mimeapps.list` has no user override by default, so the system-wide `/usr/share/applications/mimeapps.list` (owned by the `omarchy` package) wins, pointing `text/plain` and related types at `nvim.desktop` regardless of the configured default editor.

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.