Closed klobetime closed 1 year ago
@klobetime because they hijack the prompt function again, so it's pretty unreliable. You're better off enabling shell integrations in oh-my-posh, instead of adding the terminal built-in scripts. Our integration is a lot more reliable.
@klobetime you can set shell_integration
to true
in the config.
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 iTerm2 (build 3.4.20) on macOS Monterey (v12.6.7) and have enabled shell integration for bash (v5.2.15(1)-release). This combination apparently results in a non-zero exit code not being recognized:
Using iTerm2 without the integration causes oh-my-posh to behave as expected.
I get that the shell integration could be affecting how the exit code is picked up and/or interpreted, but I don't see why bash can see there is an error code of 127 (in the screenshot above) but os-my-posh does not.
Theme
What OS are you seeing the problem on?
macOS
Which shell are you using?
bash
Log output