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

omarchy default editor is ignored by file managers — text files always open in Neovim

Reported by CarloBrandolini · filed Sep 5, 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

omarchy default editor is ignored by file managers — text files always open in Neovimrevision 1 · captured 2026-10-04 12:10 UTC via poll

System details: AMD Ryzen 5 3600, AMD Radeon HD 8490, Omarchy 4.0.2-1

What's wrong?

omarchy default editor <editor> only changes the editor used by omarchy-launch-editor (which backs $EDITOR in terminals and the Omarchy menu). It does not update the XDG MIME associations, so opening a text file from a file manager (Nautilus) always launches Neovim — even though the command shows a notification claiming "Vim is now the default editor".

Steps to reproduce

  1. On a default Omarchy install, run omarchy default editor vim
  2. The setting itself is stored correctly: ~/.local/state/omarchy/defaults/editor contains vim, and omarchy default editor prints vim
  3. Open any .txt file from Nautilus → it opens in Neovim
$ omarchy default editor
vim
$ xdg-mime query default text/plain
nvim.desktop

Why (verified against master today)

  • bin/omarchy-default-editor only writes ~/.local/state/omarchy/defaults/editor and sends a notification — it never touches xdg-mime / xdg-settings / mimeapps.list.
  • default/applications/mimeapps.list hard-codes nvim.desktop for text/plain and 16 other text MIME types, so GUI file opening always resolves to Neovim regardless of the chosen editor.
  • By contrast, bin/omarchy-default-browser reads and writes the XDG handler via xdg-settings set default-web-browser, which is why omarchy default browser <x> changes what opens links everywhere.

Possible fix

Ship a desktop entry that wraps omarchy-launch-editor (e.g. Exec=omarchy-launch-editor %F, Terminal=false — it already opens TUI editors in a terminal via omarchy-launch-tui / xdg-terminal-exec) and point the text MIME types at it in mimeapps.list, so the GUI default follows the Omarchy default editor.

No debug log attached — this is a config/script issue fully reproducible from source as described above.

View raw text
**System details:** AMD Ryzen 5 3600, AMD Radeon HD 8490, Omarchy 4.0.2-1

## What's wrong?

`omarchy default editor <editor>` only changes the editor used by `omarchy-launch-editor` (which backs `$EDITOR` in terminals and the Omarchy menu). It does not update the XDG MIME associations, so opening a text file from a file manager (Nautilus) always launches Neovim — even though the command shows a notification claiming "Vim is now the default editor".

## Steps to reproduce

1. On a default Omarchy install, run `omarchy default editor vim`
2. The setting itself is stored correctly: `~/.local/state/omarchy/defaults/editor` contains `vim`, and `omarchy default editor` prints `vim`
3. Open any `.txt` file from Nautilus → it opens in Neovim

```
$ omarchy default editor
vim
$ xdg-mime query default text/plain
nvim.desktop
```

## Why (verified against master today)

- `bin/omarchy-default-editor` only writes `~/.local/state/omarchy/defaults/editor` and sends a notification — it never touches `xdg-mime` / `xdg-settings` / `mimeapps.list`.
- `default/applications/mimeapps.list` hard-codes `nvim.desktop` for `text/plain` and 16 other text MIME types, so GUI file opening always resolves to Neovim regardless of the chosen editor.
- By contrast, `bin/omarchy-default-browser` reads *and* writes the XDG handler via `xdg-settings set default-web-browser`, which is why `omarchy default browser <x>` changes what opens links everywhere.

## Possible fix

Ship a desktop entry that wraps `omarchy-launch-editor` (e.g. `Exec=omarchy-launch-editor %F`, `Terminal=false` — it already opens TUI editors in a terminal via `omarchy-launch-tui` / `xdg-terminal-exec`) and point the text MIME types at it in `mimeapps.list`, so the GUI default follows the Omarchy default editor.

*No debug log attached — this is a config/script issue fully reproducible from source as described above.*

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.