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
Not tracking num lock or caps lock for progressive enhancement #7937
Comments
This is specifically just about the Kitty keyboard protocol, right? I see no reason to track num lock or caps lock keys and I'd consider these optional (they're a progressive enhancement after all). Terminal application should not concern themselves with these keys. |
yeah, this is all in the context of kitty protocol, because they are also modifiers. |
yes, like kchibisov said, It was just something in the kitty protocol that wasn't supported so I thought I would bring it up. |
I believe @kchibisov intentionally left that out and I don't see a reason to change it. |
Forwarding is not a big deal when we have events, but as of now there's no way to do so, and I'm not sure why you want to treat capslock specially. |
Giving applications to use something they shouldn't is honestly worse than not forwarding it at all. |
I'm not sure if it's specifically alacritty's job, winit, or something else, but the num lock and caps lock state is not being tracked.
When you type the modifier, it says it changes the modifier state, but that state is actually left unchanged.
I put logs at the bottom, and neither caps lock, nor num lock change the modifier keys state.
the message makes it seem like it's on winit's side, but I didn't want to go upstream without checking first because I don't know enough.
Normally, I don't see this being an issue, but kitty's Progressive Enhancement is supposed to send it as a part of the modifiers on a key.
https://sw.kovidgoyal.net/kitty/keyboard-protocol/#modifiers
(the modifiers themselves still work as expected, they are just not tracked properly)
I also wanted to test the hyper and meta keys (as in the spec) but I honestly don't know what those keys are, how they are different than super, or how I would even send them.
Wonderful terminal, thanks for all your hard work.
System
OS: Linux Nixos unstable
Version:
alacritty 0.13.2
On Hyprland
Logs
neither actually change the modifier state when pressed, while other mods do. (not tested with hyper or super)
num lock:
caps lock:
specifically:
and
when the keys are pressed, and the modifier state says it has changed, but doesn't actually change.
what shift outputs:
this line shows the SHIFT mod being pressed:
The text was updated successfully, but these errors were encountered: