From 62dce86b4e3894e11ee355fe53eecdbc6da52803 Mon Sep 17 00:00:00 2001 From: Gabriel Brown Date: Fri, 21 Aug 2026 00:45:15 -0400 Subject: [PATCH] Let the prompt survive not being installed yet oh-my-posh moved from a curl installer to a Fedora package, and the shell config invoked it unconditionally. That is fine during a full install, where install-packages runs before the bashrc is linked -- and not fine in every other order: a stage re-run by hand, an install that failed partway, or the moment between removing the old binary and installing the package. Same guard as the nvm source above it. An unthemed prompt is a worse shell; one printing command-not-found before every prompt is a machine that looks broken. Claude-Session: https://claude.ai/code/session_01Q84axqUE5inJhf5Jz9CFy1 --- config/bash/shell | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/config/bash/shell b/config/bash/shell index 9002cf5..f4d3af8 100644 --- a/config/bash/shell +++ b/config/bash/shell @@ -43,4 +43,11 @@ fi eval "$(zoxide init bash)" # Oh My Posh -eval "$(oh-my-posh init bash --config $PANAMA_PATH/config/dot/ohmyposh/gib.omp.json)" +# Guarded for the same reason the nvm source above is: oh-my-posh is a package, +# and a shell opened before it is installed -- a stage re-run by hand, an +# install that failed partway -- would otherwise print command-not-found on +# every prompt. An unthemed prompt is a worse shell; an erroring one is a +# broken-looking machine. +if command -v oh-my-posh >/dev/null 2>&1; then + eval "$(oh-my-posh init bash --config "$PANAMA_PATH/config/dot/ohmyposh/gib.omp.json")" +fi