Roman Perepelitsa
Roman Perepelitsa
Most likely wrong `TERM`.
This fork is used only by gitstatusd. These functions aren't used there.
Thanks for checking!
It's unlikely I'll ever be making any change in this repo.
> Why not? It's work. > And what about pushing your changes upstream? Is it feasible? Might be feasible. I won't be doing it though.
I most likely will do nothing.
Sure, if you send a clean PR, I'll merge it.
FWIW, my personal advice would be to not use gitstatus. If I manage to muster enough will power for the final contribution to gitstatus/powerlevel10k, that would be getting rid of...
Must be possible but it's work. The good thing is that you can try various solutions for yourself and see whether plain git is fast enough *for you*.
There is `POWERLEVEL9K_DISABLE_GITSTATUS=true` but it incidentally also disables async git status computation. My remark above referencing *the final contribution* was about removing this coincidence.