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
Windows: Read System32 from PATH in WSL more picky #5309
Labels
Comments
The start point to improve the logic is commads_cache. |
anki-code
changed the title
xonsh in WSL, slow startup due to PATH pollution
Read System32 from PATH in WSL more picky
Mar 24, 2024
anki-code
changed the title
Read System32 from PATH in WSL more picky
Windows: Read System32 from PATH in WSL more picky
May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First of all, I have to say that I love the work you have done for xonsh! It is an awesome tool and hope that it gets the recognition it deserves in the future!
So, I am using xonsh in WSL in Windows 11. I have tried both in Debian WSL and Ubuntu WSL, with both the xonsh installed through apt and through pipx.
The problem I face is that there is a big startup time for xonsh of around 2-3 seconds. I searched a bit around and found out that the reason is that the PATH variable in WSL is too long (both in length and in terms of programs) because Windows append the PATH with the Windows PATH.
I was able to stop that from happening, and have normal startup times, by following this microsoft doc: https://learn.microsoft.com/en-us/windows/wsl/wsl-config#configure-per-distro-launch-settings-with-wslconf
Bellow in the Showcase section you can see the difference and steps to reproduce it.
So my question is basically if there is another way to handle this, instead of just removing the Windows PATH?
Also maybe this should also be documented somewhere in the docs?
xonfig
Expected Behavior
Startup time < 1sec.
Current Behavior
Startup time > 2sec.
Showcase
Steps to Reproduce
Install WSL in Windows 11 and follow the steps as shown in the above showcase
For community
⬇️ Please click the 👍 reaction instead of leaving a
+1
or 👍 commentThe text was updated successfully, but these errors were encountered: