-
-
Notifications
You must be signed in to change notification settings - Fork 923
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
Ctrl+Shift + other key stops working after first press #7460
Comments
Does not reproduce for me running up to date kitty under wayland. I |
I am able to recreate it on 0.34 as well.
On nightly, however, I do NOT seem to have this issue, so it seems to be fixed sometime between them...
|
I tried in hyprpand as well. does not replicate. I suggest setting wayland_enable_ime no in your kitty.conf. And you can run with --debug-input to see what input |
I completely forgot about IME. I do have a Japanese keyboard set up and with wayland_enable_ime yes, it works normally aside from this. Anyways, I don't particularly care for IME input on terminal so that seems to solve the issue when on 0.34. Here's the output from kitty on 0.34 (latest, not-nightly) with --debug-input when pressing Ctrl, Shift, and then t repeatedly, with twayland_emable_ime yes. It seems not to match KeyPress to action after the first two.
On same version, wayland_enable_ime no, no issues but no Japanese input:
Output from nightly with wayland_enable_ime yes, where I have no issues and japanese input works on kitty:
|
Describe the bugs
No longer able to continuously press the same key combination without taking fingers of all keys. More concretely:
Press Ctrl
Press Shift
Press T -> makes new tab
Release T
Press T -> types letter t instead of new tab
Release T
Release Shift
Release Ctrl
If I want to make multiple tabs I must press all three and release all three before repeating. This behavior repeatable every time with Ctrl+Shift+T but is inconsistent with other key binds like Ctrl+Shift+]
I have verified my keyboard is not having issues with online keyboard tester +
wev
.To Reproduce
Steps to reproduce the behavior:
Screenshots
My relevant portion of kitty conf:
Environment details
Additional context
Still occurs with
kitty --config NONE
.Let me know what additional information I can provide. Thanks again for all your work!
The text was updated successfully, but these errors were encountered: