Using shift+<key> sends ansi code, previews not working, etc

[Universal-Invariant]

What system are you running Yazi on?

Windows

What terminal are you running Yazi in?

Wezterm nightly

yazi --debug output

Yazi
    Version: 25.5.31 (b65a880 2025-05-30)
    Debug  : false
    Triple : x86_64-pc-windows-msvc (windows-x86_64)
    Rustc  : 1.87.0 (17067e9a 2025-05-09)

Ya
    Version: 25.5.31 (b65a880 2025-05-30)

Emulator
    TERM                : Some("wezterm")
    TERM_PROGRAM        : Some("WezTerm")
    TERM_PROGRAM_VERSION: Some("20251005-110037-db5d7437")
    Brand.from_env      : Some(WezTerm)
    Emulator.detect     : Emulator { kind: Left(WezTerm), light: false, csi_16t: (10, 23), force_16t: true }

Adapter
    Adapter.matches    : Iip
    Dimension.available: Dimension { rows: 44, columns: 239, width: 0, height: 0 }

Desktop
    XDG_SESSION_TYPE           : None
    WAYLAND_DISPLAY            : None
    DISPLAY                    : None
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Describe the question

When I try to rename a file and use something like shift+_ I get an ansi code: E.g., "[45:95;130u"

Not sure if these are related but it suggests it could be an issue with yazi rather than wezterm:
wezterm/wezterm#3124

This does not happen in a windows terminal so seems to be something related to wezterm. It seems that during rename(and I guess other things) the ansi escape code is not properly handled.

Also, I cannot exit out of renaming a file except by deleting all the chars and hitting enter. Esc does nothing.

Anything else?

No response

Checklist

• I have read all the documentation
• I have searched the existing discussions/issues

[Universal-Invariant]

Seems to be related to:

#2474

setting
enable_kitty_keyboard = false
in wezterm does work. This also seems to fix previews which was not working. I believe everything was working until, I updated yazi to a nightly.

[sxyazi]

I took another look at that PR and found crossterm (the underlying terminal library used by Yazi) does not support the kitty keyboard protocol on Windows at all because it uses the old Windows API instead of the newer ConPTY-based VT sequences, while the kitty keyboard protocol is VT-based.

Which means that PR has never worked as intended, and it could cause the kitty keyboard protocol sequences which crossterm cannot parse, to be enabled on Windows, so I reverted it in #3250, hope this fixes your issue, and thank you for bisecting to that PR!