Windows nightly responds '0' (mode not recognized) to DECRQM 2027

[rockorager]

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

20231030-074559-75909682

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 querying for Unicode Core support (Mode 2027), wezterm on linux responds with DECRPM 3 (permanently enabled). On Windows, I get a '0' (mode not recognized)

To Reproduce

On windows, maybe in WSL:

printf "\033[?2027\$p" && cat

Configuration

no config

Expected Behavior

Expected response CSI ? 2027 ; 3 $ y

Logs

No response

Anything else?

No response

[wez]

If you use wezterm ssh to login to a remote unix system, does that reproduce?
If that works as expected then this is a conpty issue and may require something along the lines of these upstream MS terminal issues:

• ConPTY Passthrough mode  microsoft/terminal#1173
• Conpty "pass-through" doesn't maintain order of operations microsoft/terminal#8698

to make progress, and then update the bundled conpty binaries we ship with wezterm before this will work as expected.

[rockorager]

On Sat Nov 4, 2023 at 8:45 AM CDT, Wez Furlong wrote: If you use `wezterm ssh` to login to a remote unix system, does that reproduce? If that works as expected then this is a conpty issue and may require something along the lines of these upstream MS terminal issues:

Yes, that works. Thanks for the update!

[rockorager]

* [Conpty "pass-through" doesn't maintain order of operations microsoft/terminal#8698](https://github.com/microsoft/terminal/issues/8698)

Ah this one explains an entirely different issue I saw related to query responses (getting DA1 response out of order)