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
If you are working on a pretty big git project and the git plugin is enabled in oh-my-posh, changing the current directory to that repository can cause the prompt to get stuck for a few seconds until it determines the branch we are on. And determining the branch can be slow when the repo is quite big.
The log below shows 1446ms, but at times when the system is under heavy load or a project is building in the background, it can take a lot more. My suggestion would be, if the plugin takes, for example, more than 300ms to determine the branch, it skips the check and updates it later when the process is done. Slightly related to #5036
@TheChilledBuffalo the only solution for this is to disable fetching the status for those repos using ignore_status. It's git being slow, not oh-my-posh.
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?
If you are working on a pretty big git project and the git plugin is enabled in oh-my-posh, changing the current directory to that repository can cause the prompt to get stuck for a few seconds until it determines the branch we are on. And determining the branch can be slow when the repo is quite big.
The log below shows 1446ms, but at times when the system is under heavy load or a project is building in the background, it can take a lot more. My suggestion would be, if the plugin takes, for example, more than 300ms to determine the branch, it skips the check and updates it later when the process is done. Slightly related to #5036
Theme
tokyonight_storm
What OS are you seeing the problem on?
Windows
Which shell are you using?
powershell
Log output
The text was updated successfully, but these errors were encountered: