-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Wrong key events when Num Lock is active #3587
Comments
I am having this issue. I know this is an odd use case, but it interferes with a custom binding on Backspace / Ctrl+Backspace input. kitty 0.36.2 Please let me know if more information is needed, or ideally, if there is already a simple kitty.conf toggle for numlock applying to non-numerical inputs - I have not been able to find one. |
Numlock is not used/active in kitty keybindings. This issue was about the unicode input kitten and has already been fixed long ago. |
Ah, sorry, the 'custom binding' I mentioned was for ble.sh running in kitty, not a kitty keybind. The binding functions in other terminals regardless of numlock, and in kitty when numlock is turned off, but does not function in kitty while numlock is active. Until now I had not known/understood that kitty has 'kittens' or that there is one for unicode character input. Now that I do - I think my issue is different because it affects all command-line text input in kitty. Should I create a new issue for it? |
You need to report the issue to ble.sh, not kitty. Presumably it is not |
As per my last comment, this issue is unique to kitty, and I have been using ble.sh without the issue for years. It generally handles numlock and capslock like text editors do. However, upon further research, I was able to find several ble.sh settings for handling quirks of kitty, and one of them solved my issue: Thank you for your input. |
On Sun, Oct 06, 2024 at 08:10:24AM -0700, Ian Off wrote:
As per my last comment, this issue is unique to kitty, and I have been using ble.sh without the issue for years. It generally handles numlock and capslock like text editors do.
However, upon further research, I was able to find several ble.sh settings for handling quirks of kitty, and one of them solved my issue:
https://github.com/akinomyoga/ble.sh/blob/32f290df78554e22d7ff779d34f1dfec271c16df/blerc.template#L409
Quirks of kitty indeed. That's the kitty keyboard protocol the thing
that has *finally* got sanity to input handling for terminals. Which
ble.sh apparently turns on and then doesn't parse correctly.
|
Yes, ble.sh turns on it.
Could you provide the steps to reproduce this? As far as I test it with kitty 0.31.0 and 0.36.4, ble.sh correctly parses those bits in CSI sequences and correctly ignores them. |
If Num Lock is active, key events like
Num Lock+<key>
are generated when e.g. arrow keys are pressed.To Reproduce
Steps to reproduce the behavior:
kitty +kitten key_demo
withNum Lock
activated.Expected behavior
Should generate an event pair like
The significance of the problem is that I cannot use the arrow keys to navigate in the Unicode Input kitten's name mode when Num Lock is active. They work fine when Num Lock is not active.
Environment details
OS: Arch Linux
Additional context
The problem can be reproduced with
kitty --config NONE
The text was updated successfully, but these errors were encountered: