-
-
Notifications
You must be signed in to change notification settings - Fork 781
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
Cannot input many unicode characters on windows on some applications #5260
Comments
I just found that this exact scenario does not work on WSL either, albeit with different symptoms. In WSL on cmd.exe typing unicode in helix just works. In Wezterm however, I only see replacement glyphs trying to type 𝓒: This used to work in WSL, strangely enough, as can be observed from the upper sentence. Here is the binary dump of what is actually inserted in the terminal:
|
As stated, this issue does not occur in other terminal emulators, just on wezterm. |
May you show the same input/output as screenshot in one of the other terminal emulators? |
What you can do to investigate this behavior is to find which font file delivers the glyphs and then put this file into the list of fallback fonts wezterm will use in case the specified default font does not come with required glyph. If I understand it right ezterm allows you to decide about the order of fallback font files used excluding these ones not listed ... it is a feature which makes it necessary to specify the font files to use in the configuration. |
Have you tried to put the font which provides the missing glyphs to the list of wezterm fallback fonts? With what effect? |
It's not a font problem, because nothing is inserted. And on WSL something is inserted, but not a valid single character. If it were a font problem, you would see a single replacement glyph. So probably some characters are stripped out, possibly by conpty. I'm unsure why the effect is different when running a wsl shell. I'm also unsure why other terminal emulators do not have this problem. Possibly because they interact differently, or with a different version of conpty? I'm not well versed in terminal emulator technicalities, this is mostly handwaving from my part. |
So you haven't tried to put the font to the list of wezterm fallback fonts? Sometimes it is a good idea to try also what seems not to make sense ... It turns often out that one think it does not make sense because the assumptions which lead to this conclusion were wrong ... so just trying something what does not make sense gives sometimes surprising results leading finally to a solution. |
I tried it, it doesn't help. Two other things I noticed:
|
I discovered that the virus scanner on my PC silently messed up the nightly wezterm installer without me noticing. I guess it was conpty after all, since that has been updated recently e7fe7c0 |
I spoke too soon. It is only fixed for WSL. |
In the broken scenario, what does the process tree look like, and what does the working process tree look like? wezterm -> cmd -> helix ? are you using Running through https://wezfurlong.org/wezterm/troubleshooting.html#debugging-keyboard-related-issues might be useful; ISTR that there is a some debug output that that enables that will show you what wezterm is trying to paste in. |
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
20240325-093507-e5ac32f2
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
I cannot input certain characters on wezterm in helix or nushell. If I try, nothing happens. Nothing is being inserted.
Unicode characters that cannot be input: 🎉𝓒
Unicode characters that are not a problem: ✅
On other terminal emulators, like cmd.exe, this is issue does not occur.
To Reproduce
Copy 🎉 or 𝓒 to your clipboard and try to insert it on a wezterm instance on windows while running nushell or helix.
Configuration
no config
Expected Behavior
I expected the same behavior as on cmd.exe, where the unicode characters are inserted as expected.
Logs
No response
Anything else?
The text was updated successfully, but these errors were encountered: