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

try shell function intercepts try init on re-source of bashrc

Reported by oren · filed Mar 7, 2026Closed upstream on 2026-03-07 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

try shell function intercepts try init on re-source of bashrcrevision 1 · captured 2026-10-04 11:49 UTC via poll

When running source ~/.bashrc in an already-initialized shell, the try interactive directory selector launches unexpectedly.

In default/bash/init, the line:

eval "$(SHELL=/bin/bash try init ~/Work/tries)"

calls the try shell function (defined on first source) instead of the /usr/bin/try binary. The function wraps all args through exec, so init gets misinterpreted and the interactive selector launches.

Fix: Change try init to command try init:

eval "$(SHELL=/bin/bash command try init ~/Work/tries)"
View raw text
When running `source ~/.bashrc` in an already-initialized shell, the `try` interactive directory selector launches unexpectedly.

In `default/bash/init`, the line:
```bash
eval "$(SHELL=/bin/bash try init ~/Work/tries)"
```
calls the `try` shell function (defined on first source) instead of the `/usr/bin/try` binary. The function wraps all args through `exec`, so `init` gets misinterpreted and the interactive selector launches.

**Fix:** Change `try init` to `command try init`:
```bash
eval "$(SHELL=/bin/bash command try init ~/Work/tries)"
```

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.