Andy Kipp

@gnat thanks for the test! Your test is a bit not correct because you reinstall package without restart xonsh. And after restart I have no confidence that during the run...

@gnat I think you can unpack AppImage, reinstall ptk, and test: ```xsh cd /tmp wget https://github.com/xonsh/xonsh/releases/download/0.15.1/xonsh-x86_64.AppImage chmod +x xonsh-x86_64.AppImage ./xonsh-x86_64.AppImage --appimage-extract ./xonsh-x86_64/bin/xonsh xpip uninstall prompt-toolkit xpip install prompt-toolkit==3.0.40 exit ./xonsh-x86_64/bin/xonsh...

@gnat new version have come, please test

@gnat please provide more details: `xonfig` output, operation system, any details you think helpful. Workaround: `./xonsh --shell-type readline`

I found issue in prompt-toolkit 3.0.40 too - #5393. It looks like we need to downgrade prompt-toolkit to 3.0.39. @doronz88 could you please try 3.0.39? ```xsh xpip install -U --force-reinstall...

I'm gogint to close this until new info or fix in upstream - https://github.com/prompt-toolkit/python-prompt-toolkit/issues/1853

Timing wasn't help. But I dive into the code and found the cause. In WSL2 user has very rich PATH (by default!) with many directories with huge amount of files...

### 🟢 The solution from https://github.com/microsoft/WSL/issues/1493#issuecomment-580643734: 1. Check that your PATH contains Windows directories: `echo $PATH`. 2. Create `/etc/wsl.conf`: ``` [Interop] appendWindowsPath = False ``` 4. Restart WSL2 in Powershell...

What about adding `$XONSH_WSL_REMOVE_WIN_PATH=True` to [Windows OS environment variables](https://xon.sh/envvars.html#windows-os) to check the [`platform.ON_WSL`](https://github.com/xonsh/xonsh/blob/f4e979a2f3fb7b8a919416f8d39db76f2a6ca027/xonsh/platform.py#L87C1-L90) and apply [the code like from daddycocoaman](https://github.com/xonsh/xonsh/issues/3895#issuecomment-1289471170) ? e.g. ```xsh # somewhere around loading xonshrc from xonsh.platform...

I see the root of the issue in that all files in `System32` directory are marked as executable in WSL and they are go to commands_cache but we need only...