[X] I agree to follow this project's Code of Conduct
What happened?
The line 'eval "$(oh-my-posh init bash --config ~/.mdove.omp.json)"' exists as the last line in my .bashrc. .bash_profile is a single line " if [ -f ~/.bashrc ]; then . ~/.bashrc; fi".
I create a new login shell on this Linux instance (via SSH), and everything "appears" as expected. My oh-my-posh profile is being read and displays my configuration colors/segments correctly. However, as soon as I "cd" to any other directory, the path segment doesn't update, and remains a "~".
BUT, if I simply re-run 'eval "$(oh-my-posh init bash --config ~/.mdove.omp.json)"' from the command line, it "resolves" itself, and now displays the directory I changed to, and works as I move around going forward.
The same set of .bash_profile, .bashrc work under MacOS (multiple versions) with bash 5.2 variants as well as Debian systems (variety of raspi's) with bash 5.2 variants without this issue. Is this an issue with the 5.0 bash on these particular (AWS) instances?
In the debug log below, you'll notice I had switched to a directory named "Development", however the prompt which gets displayed to me is "~".
Code of Conduct
What happened?
The line 'eval "$(oh-my-posh init bash --config ~/.mdove.omp.json)"' exists as the last line in my .bashrc. .bash_profile is a single line " if [ -f ~/.bashrc ]; then . ~/.bashrc; fi".
I create a new login shell on this Linux instance (via SSH), and everything "appears" as expected. My oh-my-posh profile is being read and displays my configuration colors/segments correctly. However, as soon as I "cd" to any other directory, the path segment doesn't update, and remains a "~".
BUT, if I simply re-run 'eval "$(oh-my-posh init bash --config ~/.mdove.omp.json)"' from the command line, it "resolves" itself, and now displays the directory I changed to, and works as I move around going forward.
The same set of .bash_profile, .bashrc work under MacOS (multiple versions) with bash 5.2 variants as well as Debian systems (variety of raspi's) with bash 5.2 variants without this issue. Is this an issue with the 5.0 bash on these particular (AWS) instances?
In the debug log below, you'll notice I had switched to a directory named "Development", however the prompt which gets displayed to me is "~".
Theme
Personal theme based originally on Jan's
What OS are you seeing the problem on?
Linux
Which shell are you using?
bash
Log output