Sixel image protocol doesn't work on Windows

[0x6675636b796f75676974687562]

What Operating System(s) are you seeing this problem on?

Windows

Which Wayland compositor or X11 Window manager(s) are you using?

No response

WezTerm version

20240623-130118-4daab4dc

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

When running a Windows version of WezTerm, Sixel image protocol doesn't work.

To Reproduce

1. Connect a Windows version of WezTerm to a Linux box, over SSH or WSL.
2. Install img2sixel to be able to display images in your terminal: apt-get install img2sixel on Debian/Ubuntu.
3. Alternatively, get a sixel file you can display via cat.
4. Run cat image.six. The image will not get displayed.
5. Run img2sixel image.png. The image will not get displayed.

Configuration

no config

Expected Behavior

No response

Logs

No response

Anything else?

No response

[0x6675636b796f75676974687562]

Reference rendering: XTerm

[0x6675636b796f75676974687562]

Correct rendering: Wezterm on Linux (via X11):

[0x6675636b796f75676974687562]

No rendering: WezTerm on Windows

[AnonymouX47]

Duplicate of #1236

See also #1237

[github-actions[bot]]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.