You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if this has already been answered elsewhere. I did my best to search for relevant information first, but I couldn't find what I was looking for.
When the BranchBehindAndAheadDisplay setting was first introduced in #256, Minimal would show ↑, ↓, or ↕ as appropriate with no counts. As of commit 4d8e08c, Minimal does not show any arrows, but the branch name is still colored red/green/yellow.
Was this a deliberate change? Obviously the color is sufficient to indicate its remote tracking status, but it seemed odd to me that the arrows would be removed given that it still displays the ≡ symbol when the branch is even with its remote. I couldn't find an issue where this might have been discussed, and it's not mentioned in the changelog for version 0.7.3, which was the next release after that commit.
I only noticed because I was working on an equivalent feature for lyze/posh-git-sh#37 and I wanted to ensure it behaved the same. I like Full myself 😃
Thanks for all your work! posh-git is fantastic.
The text was updated successfully, but these errors were encountered:
System Details
Issue Description
Apologies if this has already been answered elsewhere. I did my best to search for relevant information first, but I couldn't find what I was looking for.
When the
BranchBehindAndAheadDisplay
setting was first introduced in #256,Minimal
would show ↑, ↓, or ↕ as appropriate with no counts. As of commit 4d8e08c,Minimal
does not show any arrows, but the branch name is still colored red/green/yellow.Was this a deliberate change? Obviously the color is sufficient to indicate its remote tracking status, but it seemed odd to me that the arrows would be removed given that it still displays the ≡ symbol when the branch is even with its remote. I couldn't find an issue where this might have been discussed, and it's not mentioned in the changelog for version 0.7.3, which was the next release after that commit.
I only noticed because I was working on an equivalent feature for lyze/posh-git-sh#37 and I wanted to ensure it behaved the same. I like
Full
myself 😃Thanks for all your work! posh-git is fantastic.
The text was updated successfully, but these errors were encountered: