-
-
Notifications
You must be signed in to change notification settings - Fork 982
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
Improve keyboard layout handling #2000
Comments
Actually the Russian keyboard layout should work, I'm pretty sure I added all the keys for it. |
Oh right, then for other people with weird symbols 😃 Either way, it would be nice to be able to make kitty-shortcut that are layout independent, using a special syntax like (or |
Is there any progress on this? I have the same issues with the neo layout. |
Re Russian layout. Some time ago after Kitty update I've noticed a problem: no shortcuts work when Russian layour is selected. For example, I've used to be able to press Can it be reverted until you find a proper solution? Because it worked before. BTW, strangely, I started to experience the same problem on macOS recently. |
Hi, sorry didn't see your message. I don't have much time for personal projects currently, so no, no progress on this. Also as I'm (unfortunately) forced to use windows at work (and have some of the same problems, but it's another topic ^^) I don't really use kitty at the moment. |
@kovidgoyal hi, can you also please respond to my problem above (#2000 (comment))? |
Use debug keyboard to see what keys w and c are in your layout and map them using send_textto send the bytes corresponding to ctrl_w and ctrl+c |
Well, this is rather clumsy, given that it used to work. Could you revert the change that broke it? |
This has already been discussed elsewhere, read up on it, or if you dont have the time, just implement the workaround. |
Here is the issue where this has been discussed: #606. I think some of the comments towards the bottom might be what you're looking for but I would recommend reading the entire issue. |
So for anyone finding this issue in the future, here are bindings for most basic keys (^C, ^D, ^H, ^W):
This will make them "work" on Russian layout the same way as they do on English. |
…y matches an English key in the default layout, send that to the program running in the terminal automatically See #2000
This should be fixed in master, though I have not tested it much given I only have standard pc keyboards. |
Here is mine solution. Actually, the idea is the same to map each shortcut for the non-Latin character, but I made automated script to do that. https://jakeroid.com/blog/kitty-shortcuts-work-only-with-latin-characters-how-to-fix |
This issue will track progress and discussion to improve keyboard layout handling. (continuing the discussion started in #1980)
TL;DR: #1990 & #1980 should work out of the box.
What
Make 'composed' shortcut work with any modifiers (need to rephrase?)
With the french keyboard layout, typing
shift+:
should send/
to the terminal app, andalt+shift+:
should send^[/
.The former already works, but the latter does not send anything (this is the problem description of #1980).
Same problem with #1980 (comment) (
alt+altgr+"
should givealt+#
).Handle non-standard modifiers from keyboard layouts
Given
some_mod+X
withsome_mod
a non standard mod likeISO_Level2_Shift
.Currently when X is a key that exist directly in the US layout, the resulting key is the shifted version of the matching US layout key (was done because of #171 (comment)).
This would also fix #1990.
→ Correct layout handling should fix this automatically
Allow kitty shortcut using resolved keys and real pressed keys
To make
map alt+shift+: ...
work the same asmap alt+/ ...
→ This will be easy once we make GLFW report both on a key event!
Idea - keyboard layout agnostic Kitty shortcut
It would be nice to have layout-independent kitty-shortcut, using a special syntax like map @ctrl+shift+c ... (we're back to #606..), so that you can switch between (e.g) French and Russian and still be able to use these Kitty shortcuts.
(or
map! ctrl+shift+c ...
to avoid any key clash and give a kind of semantic "it should always work!!")Existing behaviors to keep
How
The idea is to check with xkbcommon the modifiers consumed by the resulting key (ex:
shift
forshift+:
)I'll update this post when I find other things!
The text was updated successfully, but these errors were encountered: