Error messages after upgrading oh-my-posh

[mtrolley]

brew gist-logs <formula> link OR brew config AND brew doctor output

❯ brew config
HOMEBREW_VERSION: 4.5.4-39-g1f37a11
ORIGIN: https://github.com/Homebrew/brew
HEAD: 1f37a11b7946b6d770ecba66a487ba325b58e49c
Last commit: gpg: Signature made Fri Jun  6 12:45:40 2025 EDT
gpg:                using RSA key B5690EEEBB952194
gpg: Can't check signature: No public key
21 hours ago
Branch: master
Core tap JSON: 07 Jun 13:23 UTC
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 16
HOMEBREW_NO_ENV_HINTS: set
HOMEBREW_SORBET_RUNTIME: set
Homebrew Ruby: 3.4.4 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/3.4.4/bin/ruby
CPU: 16-core 64-bit skylake
Clang: N/A
Git: 2.34.1 => /bin/git
Curl: 7.81.0 => /bin/curl
Kernel: Linux 5.15.0-141-generic x86_64 GNU/Linux
OS: Ubuntu 22.04.5 LTS (jammy)
Host glibc: 2.35
/usr/bin/gcc: 11.4.0
/usr/bin/ruby: N/A
glibc: N/A
gcc@11: N/A
gcc: 15.1.0
xorg: N/A

❯ brew doctor
Your system is ready to brew.

Verification

• My brew doctor output says Your system is ready to brew. and am still able to reproduce my issue.
• I ran brew update and am still able to reproduce my issue.
• I have resolved all warnings from brew doctor and that did not fix my problem.
• I searched for recent similar issues at https://github.com/Homebrew/homebrew-core/issues?q=is%3Aissue and found no duplicates.

What were you trying to do (and why)?

I get error mesages every time I upgrade oh-my-posh until I run eval "$(oh-my-posh init zsh --config $HOME/.config/oh-my-posh/theme.omp.json)".

I don't know if there's anything that can be done to avoid this when installing this package with Homebrew, so I wanted to ask.

What happened (include all command output)?

_omp_preexec:5: no such file or directory: /home/linuxbrew/.linuxbrew/Cellar/oh-my-posh/26.3.0/bin/oh-my-posh
_omp_get_prompt:3: no such file or directory: /home/linuxbrew/.linuxbrew/Cellar/oh-my-posh/26.3.0/bin/oh-my-posh

What did you expect to happen?

I'm hoping there's some way to allow the package to upgrade seamlessly without having to manually re-initialize the prompt.

Step-by-step reproduction instructions (by running brew commands)

brew upgrade oh-my-posh

[carlocab]

What's the output of

oh-my-posh init zsh --config $HOME/.config/oh-my-posh/theme.omp.json

?

Feel free to dump it in a text file if it's very verbose.

[mtrolley]

In a tmux session that I haven't reloaded the OMP config yet (you'll need to scroll right, I didn't change the formatting and the second error is pushed off to the right with a bunch of whitespace):

❯ oh-my-posh init zsh --config $HOME/.config/oh-my-posh/theme.omp.json
_omp_preexec:5: no such file or directory: /home/linuxbrew/.linuxbrew/Cellar/oh-my-posh/26.3.0/bin/oh-my-posh
source $'/home/trolley/.cache/oh-my-posh/init.26.4.0.9a745e561709e405.5.zsh'%                                          _omp_get_prompt:3: no such file or directory: /home/linuxbrew/.linuxbrew/Cellar/oh-my-posh/26.3.0/bin/oh-my-posh

In one that I have:

❯ oh-my-posh init zsh --config $HOME/.config/oh-my-posh/theme.omp.json
source $'/home/trolley/.cache/oh-my-posh/init.26.4.0.9a745e561709e405.5.zsh'%

[dizthewize]

I am currently facing this same issue when I run brew upgrade the terminal hangs when install oh-my-posh. I am using a url to get the theme from the oh my posh git repository here is the final line of my .bashrc file

eval "$(oh-my-posh init bash --config 'https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/atomic.omp.json')"

Here's the output the terminal gets stuck on when I run brew upgrade
-bash: /home/linuxbrew/.linuxbrew/Cellar/oh-my-posh/25.23.3/bin/oh-my-posh: No such file or directory
-bash: /home/linuxbrew/.linuxbrew/Cellar/oh-my-posh/25.23.3/bin/oh-my-posh: No such file or directory

[mtrolley]

That's a great point r.e. Bash. I use ZSH and just get the error messages. When I have been using it in Bash it got into some kind of error state where I couldn't even close the shell. I had to completely close the terminal window and start again.

I rarely use Bash though, so don't have logs or error messages for that.