Skip to content
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

Adding support for different keyboard layouts #184

Open
timseriakov opened this issue Jul 3, 2023 · 3 comments
Open

Adding support for different keyboard layouts #184

timseriakov opened this issue Jul 3, 2023 · 3 comments

Comments

@timseriakov
Copy link

Currently I’m a happy user of kindaVim and appreciate its functionality. However, I have a suggestion that I believe will make it even more convenient for many users.

Problem:
Currently, kindaVim works perfectly for text written in Latin characters. However, when it comes to using Vim bindings for working with non-Latin text, such as Cyrillic, there are challenges. Users have to go through the additional step of switching keyboard layouts, which can be inconvenient and disrupt the workflow.

Proposal:
I would like to propose adding a feature to kindaVim that allows for duplicated key mappings for different keyboard layouts. This means that users can have duplicate bindings specifically for non-Latin text, such as Cyrillic, and use kindaVim without the need to switch keyboard layouts.

Another alternative solution could be to rely on universal key codes for keyboard inputs, which would be independent of the current keyboard layout.

By implementing either of these features, kindaVim would become much more accessible and practical for users who work with non-Latin text and rely on Vim bindings.

Thank you for considering my suggestion!

@godbout
Copy link
Owner

godbout commented Jul 3, 2023

CSS is easy. It’s like riding a bike, which is on fire and the ground is on fire and everything is on fire because it is hell.

🤣️🤣️🤣️🤣️🤣️🤣️🤣️🤣️🤣️

@godbout
Copy link
Owner

godbout commented Jul 3, 2023

WILL BE THINKING OUT LOUD HERE

Currently I’m a happy user of kindaVim

ok that's all i need to know bye 😂️

Problem: Currently, kindaVim works perfectly for text written in Latin characters. However, when it comes to using Vim bindings for working with non-Latin text, such as Cyrillic, there are challenges. Users have to go through the additional step of switching keyboard layouts, which can be inconvenient and disrupt the workflow.

ok so you mean like if i have a text in Russian, then i can't use kV right? can you paste something so that i can try how kV behaves and how Vim itself behaves? thanks.

Proposal: I would like to propose adding a feature to kindaVim that allows for duplicated key mappings for different keyboard layouts. This means that users can have duplicate bindings specifically for non-Latin text, such as Cyrillic, and use kindaVim without the need to switch keyboard layouts.

my feel is that for custom mappings, this will never be done natively in kV. too much work. too crazy. AND. there are other solutions, some specialized for that: Karabiner-Elements, Hammerspoon, BTT, etc. special key mappings should be handled there. (or am i missing something?)

see #153 for some discussion

Another alternative solution could be to rely on universal key codes for keyboard inputs, which would be independent of the current keyboard layout.

i can't wrap my head exactly around this now, but i think the opposite was being asked before. some people want it one way, some people the opposite way. see #12. that being said there's still some bug or something that i'm trying to figure out. see #168.

Thank you for considering my suggestion!

of course.

that's all the comments i have for now.

@godbout
Copy link
Owner

godbout commented Sep 18, 2023

see #197 (reply in thread) for what i'm referring above regarding different people wanting different things. probably best is to handle everything through a keymapper BEFORE reaching kV. so something like Karabiner-Elements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants