Cannot input certain unicode characters on windows

[chtenb]

Summary

It's impossible to input the 🎉 character into helix, either through pasting or directly inserting (using something like wincompose).
The character ✅ poses no problem however.

Reproduction Steps

Copy the 🎉 from here and try to paste it into helix using whatever method.

Helix log

The log contains no warnings

Platform

Windows

Terminal Emulator

Tried several, including WezTerm, Windows Terminal, cmd.exe

Helix Version

Custom build based on a recent commit

[chtenb]

Possibly related issue due to shared dependencies: nushell/nushell#10578

[the-mikedavis]

Looks like an issue upstream in crossterm as they say in the nushell issue

[pascalkuthe]

yeah temrinal input (particuarly unicode) on windows is simply a mess and very hard to implement, there are other open issues about that (crossterm-rs/crossterm#820, #7129). i don't think the crossterm folks would work on this themselves.The windows input fixes were made by an outside contributor who doens't appear active on the repo.

I considered fixing crossterm-rs/crossterm#820, myself but I don't ever use windows and don't have access to a windows machine for testing (and don't care enough to setup a VM just for this).

[CptPotato]

I considered fixing crossterm-rs/crossterm#820, myself but I don't ever use windows and don't have access to a windows machine for testing (and don't care enough to setup a VM just for this).

I'd be happy to test on windows, in case anyone decides to take this on.

[satorkain]

Works for me on win10. But only in WezTerm.

UPD
and in "windows-terminal"

[chtenb]

Could it be that somehow you have a different conpty version? I don't really know how this all works, but I've read somewhere that some applications ship their own version of conpty while others depend on the system installed version.
FWIW I'm on windows 11.

[satorkain]

I don't know, I have the most stripped down build of win10 that doesn't have a store or even a calculator.

[kirawi]

Wezterm packages a version of conpty with it. But this might be something else since it works in Windows Terminal.

[kirawi]

I can replicate it on Windows 11 but not Windows 10.

[pascalkuthe]

this likely should be reported against crossterm. They developed their windows handling against windows 10 I think.

[kirawi]

I will. I also rechecked and I can actually replicate this in both 10 and 11. However, Alacritty on both versions works as expected compared to Windows Terminal and Wezterm.

[pascalkuthe]

yeah wezterm uses a different API. I don't really know the ins and outs fo windows input handling but my understanding is that wezterm is the first terminal emulator besides windows terminal to use a certain API so its likely related to that API.

[kirawi]

Two possibly related issues I found were microsoft/terminal#190 and PowerShell/PSReadLine#1329

[chtenb]

this likely should be reported against crossterm. They developed their windows handling against windows 10 I think.

Should I create an issue in the crossterm issue tracker for this?

[chtenb]

This issue does not reproduce anymore for me on the latest release on cmd.exe. Not sure if fixed by windows updates or crossterm updates.

[chtenb]

Still occurs on wezterm, I created wez/wezterm#5260 for that