New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Branch Switch Delay #12378
Comments
Hi! That's expected with the new async way of getting git information. As you may feel, it's way faster to enter the directories, and you don't need to wait for git information to be ready. |
Hi @carlosala! Disabling git async fixed my problem; I appreciate the quick response! For what it's worth: on my machine and network (M2 Max w/64gb RAM) I don't notice any drops in performance with the feature enabled or disabled. I think I'll keep the feature disabled for the foreseeable future. |
Describe the bug
With the latest OMZsh update, it appears there is a lag when switching branches (video attached for example).
Previous Versions: A repo or directory would be loaded on the correct branch "right away" (apologies for lack of technical terminology). No flickering/switching present.
New/current Version: A repo or directory is loaded on an incorrect branch, and flashes/switches to the expected branch after loading the directory. In the attached video, notice the
se-commerce
andsportsengine
directories will briefly flash the previously loaded branch.Steps to reproduce
branchA
checked-out, and RepoB hasbranchB
checked-out (repo names and branches are at testers discretion)Expected behavior
A repo or directory is loaded on the expected branch "right away" (without any delay or flickering between branches).
Screenshots and recordings
Screen.Recording.2024-04-23.at.9.48.20.AM.mov
OS / Linux distribution
MacOS Sonoma 14.4
Zsh version
5.9
Oh My Zsh version
master (5d2d35c)
Terminal emulator
Terminal.app
If using WSL on Windows, which version of WSL
None
Additional context
sportsengine
is a monorepo andse-commerce
is a repo/project within the larger monorepo.The text was updated successfully, but these errors were encountered: