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
Yazi is mistaking the Windows Terminal for WezTerm. Yazi always detects either Wayland or X11, which is not available on my system (Windows Terminal with Arch in WSL). I do have some hacks in place in my WSL to make some tools work. It simulates a display, which sets the DISPLAY env var. There is no Wayland/X11 running, but some of those env variables are set.
@MarvinJWendt I am wondering if it is getting more than one of the environment variables that it uses to detect the emulator and picking the non Windows Terminal one.
If you look at your environment variables in that shell do you see the WT_Session one? And any others from this list?
@MarvinJWendt Could you share some further details in terms of what your hack/workarounds are for other applications (Or even what the requirement is, might be a case it can be fully worked around etc.)?
I've got almost the same setup (Using WSL(2) Arch in a Windows via Windows Terminal) and would like to see if I can reproduce this to have a better look into it.
What system are you running Yazi on?
Windows WSL
What terminal are you running Yazi in?
Windows Terminal
yazi --debug
outputDid you try the latest nightly build to see if the problem got fixed?
No, and I'll explain why below
Describe the bug
Bug discovered in discussion previously. (#1470 (reply in thread))
Yazi is mistaking the Windows Terminal for WezTerm. Yazi always detects either Wayland or X11, which is not available on my system (Windows Terminal with Arch in WSL). I do have some hacks in place in my WSL to make some tools work. It simulates a display, which sets the DISPLAY env var. There is no Wayland/X11 running, but some of those env variables are set.
Setting
DISPLAY
env var to empty:Setting
WAYLAND_DISPLAY
to empty string:Completely unsetting the env variables:
Minimal reproducer
yazi --debug
Anything else?
If you do not have access to a WSL instance, I would be happy to test nightlies for you.
The text was updated successfully, but these errors were encountered: