-
-
Notifications
You must be signed in to change notification settings - Fork 677
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
sixel doesn't work on Windows 10 #1236
Comments
The Windows ConPTY layer might be interfering with this. If you use |
I'm not with this Windows 10 right now, will let you know tmr. |
Yes, |
We're waiting on some combination of: before this will work directly on ConPTY |
For what it's worth, mintty is a Windows terminal that supports sixel graphics. |
@ykhan21 wezterm does support sixel graphics. It's conpty in the middle that can mess things up |
The workaround that I suggest is using |
Is there a way to get it to work without ssh-ing into a linux / WSL environment? For example, on Windows with mintty I can do: |
No, conpty, which is intimately tied to native console program output on windows, does not support sixels. As an alternative, using the iTerm2 image protocol uses a different kind of escape sequence that can mostly squeeze through conpty. Consider using eg: png or jpg images together with wezterm imgcat |
What Operating System(s) are you seeing this problem on?
Windows
WezTerm version
wezterm 20210814-124438-54e29167
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
No, and I'll explain why below
Describe the bug
when I open wezterm on windows10, ssh to remote linux, and
img2sixel path/img.png
, nothing printsTo Reproduce
open wezterm on windows10
ssh to linux server
img2sixel path/img.png
Configuration
no config
Expected Behavior
Sixel graphics support (experimental: starting in 20200620-160318-e00b076c)
Logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: