Closed metal-gabe closed 1 year ago
@gflujan that's not a bug but probably the non-official brew which had to do a fix to get the version number right using a revision. We hardly ever do fixes on existing formulae.
@JanDeDobbeleer I wanted to revisit this because it seems like your cask is now having this issue.
I just updated oh-my-posh
and the version it updated to is 18.7.0_1
, but running oh-my-posh --version
reports back 18.7.0
. Which breaks my shell paths/commands/args/etc.
I can confirm that I have used your official cask of jandedobbeleer/oh-my-posh/oh-my-posh
to install.
@gflujan the cask version and oh-my-posh version will always be different on revisions. That's not something we can solve. As I stated above, it's rare that this happens though.
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.
Code of Conduct
What happened?
I'm using the following
eval
command in my shell to initialize my OMP theme:eval "$(oh-my-posh init zsh --config "$(brew --cellar)/oh-my-posh/$(oh-my-posh version)/themes/atomicbit.omp.json")"
However, the theme is broken right now because the command
oh-my-posh version
reports17.6.0
when the actual version (and directory name) is17.6.0_1
.Theme
Atomic Bit
What OS are you seeing the problem on?
macOS
Which shell are you using?
zsh
Log output