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

nvim crashes terminal when launched via `n` bash function/alias

Reported by grumpydumpty · filed Feb 9, 2026Closed upstream on 2026-02-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

nvim crashes terminal when launched via `n` bash function/aliasrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

AMD Ryzen 9 PRO 8945Hz, AMD Radeon 780M Graphics, Omarchy 3.3.3

What's wrong?

Problem

nvim crashes terminal when launched via n bash function/alias.

When launched via SUPER + SHIFT + N, nvim opens fine.

Suspected cause

nvim calls a function in ~/.local/share/omarchy/default/bash/aliases:

n() { if [ "$#" -eq 0 ]; then nvim .; else nvim "$@"; fi; }

This causes a recursive function where nvim calls itself endlessly. I changed it to:

n() { if [ "$#" -eq 0 ]; then command nvim; else command nvim "$@"; fi; }

Which causes the function to exit its recursion and launch the actual editor.

Proposed solution

-n() { if [ "$#" -eq 0 ]; then nvim .; else nvim "$@"; fi; }
+n() { if [ "$#" -eq 0 ]; then command nvim; else command nvim "$@"; fi; }

Testing

I have been using proposed solution for a number of days now without issue. I upgraded to Omarchy 3.3.3 this morning and the issue reappeared. I reapplied the proposed solution and the issue is gone.

Attribution

Originally diagnosis and proposed solution were taken from here: nvim crashing terminal : r/omarchy.

View raw text
### System details

AMD Ryzen 9 PRO 8945Hz, AMD Radeon 780M Graphics, Omarchy 3.3.3

### What's wrong?

### Problem

`nvim` crashes terminal when launched via `n` bash function/alias.

When launched via `SUPER` + `SHIFT` + `N`, `nvim` opens fine.

### Suspected cause

nvim calls a function in `~/.local/share/omarchy/default/bash/aliases`:

`n() { if [ "$#" -eq 0 ]; then nvim .; else nvim "$@"; fi; }`

This causes a recursive function where nvim calls itself endlessly. I changed it to:

`n() { if [ "$#" -eq 0 ]; then command nvim; else command nvim "$@"; fi; }`

Which causes the function to exit its recursion and launch the actual editor.

### Proposed solution

```diff
-n() { if [ "$#" -eq 0 ]; then nvim .; else nvim "$@"; fi; }
+n() { if [ "$#" -eq 0 ]; then command nvim; else command nvim "$@"; fi; }
```

### Testing

I have been using proposed solution for a number of days now without issue. I upgraded to Omarchy 3.3.3 this morning and the issue reappeared. I reapplied the proposed solution and the issue is gone.

### Attribution

Originally diagnosis and proposed solution were taken from here: [nvim crashing terminal : r/omarchy](https://www.reddit.com/r/omarchy/comments/1pciz7g/nvim_crashing_terminal/).

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.