-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
fish became slow because checking two tools #10503
Comments
What's your |
Actually, I checked the path before, but I didn't think it was too long at the time because it can be that long under Windows; Then I compared it with another server and found that it was indeed quite long.... Thanks! Problem solved. But I still have a question. It seems that having a long PATH under Windows does not significantly slow down PowerShell or even when using oh-my-posh, does it? |
Two different issues, first is that accessing Windows paths from WSL Linux binaries is slow because of how Microsoft implemented it, second is that normal pattern is to look up commands you expect to find, which means you can stop looking as soon as you find the first match. By contrast, if you have something like #10506 attempts to work around this specific WSL issue. |
Thank you for your very good answer |
do we want changelog entries for these fixes? |
Definitely for this one. I already tagged the PR with the release notes label. |
fish, version 3.7.1
execute
fish --profile /tmp/fish.prof -c fish_prompt cat /tmp/fish.prof | sort -h
The last two rows:
these two command takes a lot of time. I don't know why this is happening, it makes my fish slow down.
My environment is in wsl2.
The text was updated successfully, but these errors were encountered: