Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Yay + fzf aliases
Reported by justbispo · filed Jul 1, 2025Closed upstream on 2025-07-03 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
I think this can be, from my own experience, a faster and more useful way of installing and searching applications.
Here's an example of the commands I use to install, remove, search the repos and search installed, respectively:
alias pari='paru --color always -Sl | sed -e "s: :/:; s/unknown-version//; s/ \[installed\]/\[installed\]/" | fzf --multi --ansi --preview "paru -Si {2} && paru -Gc {2}" --preview-window=60% --tiebreak=index --delimiter "\/|\ " | cut -d"/" -f 2 | cut -d" " -f 1 | xargs -ro paru -S'
alias parr='paru --color always -Q | fzf --multi --ansi --preview "paru -Qil {1}" --preview-window=60% | cut -d" " -f 1 | xargs -ro paru -Rns'
alias pars='paru --color always -Sl | sed -e "s: :/:; s/unknown-version//; s/ \[installed\]/\[installed\]/" | fzf --multi --ansi --preview "paru -Si {2} && paru -Gc {2}" --preview-window=60% --tiebreak=index --delimiter "\/|\ "'
alias parsi='paru --color always -Q | sed -e "s: :/:" | fzf --multi --ansi --preview "paru -Qil {1}" --preview-window=60% --delimiter "/" --bind "enter:execute(paru -Qil {1} | bat)"'I use paru but yay options are very similar with paru options (from my testing, only -c, to show AUR comments, doesn't exist in yay)
There's also a small app called yayfzf that does a similar job, but I think aliases wok well enough.
Either way, this is just an issue to get to know if this is something that you'd be interested in adding.
View raw text
I think this can be, from my own experience, a faster and more useful way of installing and searching applications.
Here's an example of the commands I use to install, remove, search the repos and search installed, respectively:
```fish
alias pari='paru --color always -Sl | sed -e "s: :/:; s/unknown-version//; s/ \[installed\]/\[installed\]/" | fzf --multi --ansi --preview "paru -Si {2} && paru -Gc {2}" --preview-window=60% --tiebreak=index --delimiter "\/|\ " | cut -d"/" -f 2 | cut -d" " -f 1 | xargs -ro paru -S'
alias parr='paru --color always -Q | fzf --multi --ansi --preview "paru -Qil {1}" --preview-window=60% | cut -d" " -f 1 | xargs -ro paru -Rns'
alias pars='paru --color always -Sl | sed -e "s: :/:; s/unknown-version//; s/ \[installed\]/\[installed\]/" | fzf --multi --ansi --preview "paru -Si {2} && paru -Gc {2}" --preview-window=60% --tiebreak=index --delimiter "\/|\ "'
alias parsi='paru --color always -Q | sed -e "s: :/:" | fzf --multi --ansi --preview "paru -Qil {1}" --preview-window=60% --delimiter "/" --bind "enter:execute(paru -Qil {1} | bat)"'
```
I use paru but yay options are very similar with paru options (from my testing, only `-c`, to show AUR comments, doesn't exist in yay)
There's also a small app called [yayfzf](https://github.com/ConnerWill/yayfzf) that does a similar job, but I think aliases wok well enough.
Either way, this is just an issue to get to know if this is something that you'd be interested in adding.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.