-
-
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
Italian keyboard: Cannot input some chars #1080
Comments
Thanks for digging in! If you have the bandwidth to poke at this a bit further, and since you have and use one of the keyboard layouts that wezterm struggles with, I'd really appreciate it if you could help us find out the path to success! The goal of the input handling is to capture, in as high-fidelity as possible, the pressed keys and then represent them in a logical and an unambiguous fashion. The code that you commented out was intended to do that, but it doesn't seem universally good. What would be super helpful to me is:
|
quick update: works with |
I haven't tested ferama's solution, but until someone finds a proper fix for this, remapping the keys that don't work is an option. use_ime = false,
send_composed_key_when_left_alt_is_pressed = true, -- my bluetooth keyboard needs "left" even if I want the "right" alt
send_composed_key_when_right_alt_is_pressed = true,
enable_csi_u_key_encoding = false,
use_dead_keys = true,
keys = {
{key="+", mods="ALT", action={SendKey={key="]"}}},
{key="ç", mods="ALT", action={SendKey={key="}"}}},
{key=" ", mods="ALT", action={SendKey={key=" "}}},
}, |
and then remove horrible mac hacks. This resolves the root cause for some horrible mac key mapping stuff that is responsible for at least 3 different user issues by making the default key assignments work from the physical key location. That makes them unambiguous. refs: #601 refs: #760 refs: #1080 refs: #1483
I think this is essentially a duplicate of two other issues, but regardless: Thanks to the groundwork laid in #1483 I just pushed a commit that fixes those other mac issues, and I think it resolves this one too. It will show up in the nightly downloads within an hour. |
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. |
What Operating System(s) are you seeing this problem on?
macOS
WezTerm version
latest, built from source too
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'm on a M1 Mac using Italian Keyboard. It seems there is no way to input chars like ']' on '}'. I can successfully input '[' and '{' instead. The ']' char on Italian keyboard require a combination of Option plus the key containing "+". The '}' instead, requires Shift+Option+ the key containing "+"
I'm absolutely new to rust but I tried to find the source of the issue. I noticed that if in this file https://github.com/wez/wezterm/blob/main/window/src/os/macos/window.rs I comment from line 1817 to line 1829 I can successfully input the chars above.
I'm not actually able to contribute with a proper fix to the issue but I hope that the hint can be helpful
To Reproduce
No response
Configuration
no config
Expected Behavior
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: