-
Notifications
You must be signed in to change notification settings - Fork 103
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
Very slow compared to Powershell posh-git #45
Comments
Currently it seems to be pretty slow (I am using WSL v1.) compared to git in powershell. But TBH I don't remember how fast/slow it was on back then, when I was trying out this extension. It might be the reason behind this extreme snowlines or might not. Not sure. |
Yes I am using WSL 2 and it is very slow on there when the git files are on the mounted C:\ drive. This is a git problem though, which is a known WSL performance problem when using /mnt files: microsoft/WSL#4197 |
I am using Ubuntu 20 in WSL2. Thanks for porting this very useful tool! Small detail: I noticed that after installing it and sourcing .bashrc, the initial coloring of the user name, host and the rest of the previous prompt is not colored anymore. That's a very minor issue, but if somebody knows how to fix it, thanks in advance :) |
I have a fairly ordinary prompt with Ubuntu.
Not seeing color might be as intended, since the README suggests
which doesn't have the color codes. Perhaps you may want to do something like this:
|
I've solved slow working in WSL2 on mounted windows filesystems by exiting early when I can create PR with some kind of env variable ( |
I have no need currently. I ended up re-cloning the repos directly into the WSL2 filesystem and stopped using anything on Windows mount. That performed perfectly for me. |
Hey,
I just installed it and it seems that it does the trick, but it is very slow compared to powershell's posh-git. After each pressed 'enter' in the console I have to wait ca 3 sec or more to actually give me a new (re-counted) line. Is this normal behavior?
The text was updated successfully, but these errors were encountered: