You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
The start point to improve the logic is commads_cache.
Probably the way to improve the logic for windows is around reading only .exe files instead of full directory.
As I remember because windows mounts the directory with assigning +x to all files we treat all of these as executable but in fact only .exe files are executable. If it's right we can change the logic for ON_WSL and System32 directory.
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: