You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since there is no discussion section, I had to ask this in this issues section. Sorry about that.
I am using non latin1 keyboard. Is it possible to remap vim default keys to something else such as h=>k, j=>k, k=>m. Of course, I would like to map some other frequently used keys to more appropriate ones according to my keyboad.
Is it possible? If yes, how can I do that? I have not seen anything in the documentation.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hey @benibilme, interesting question! And no worries, opening an issue is the right place to ask for this project.
So, my initial thought is that there is not a purpose-built feature in this package to remap keys (although there may still be a solution to your problem). In the longer term, the direction of this package will be to use neovim under the hood, at which point one could configure behavior similarly to vim/neovim.
In terms of solving your issue in the present, though, I don't think it would be too difficult to add a simple configuration option for remapping some of the keys.
You've articulated a few of the mappings you'd like to change, could you describe some of the other frequently used keys you'd like to remap? Is it solely motion commands, or would you also want to be able to remap operators (e.g. c, d)?
I ask so that I can understand how extensive a "remapping" feature would need to be.
Hello,
Since there is no discussion section, I had to ask this in this issues section. Sorry about that.
I am using non latin1 keyboard. Is it possible to remap vim default keys to something else such as
h=>k, j=>k, k=>m
. Of course, I would like to map some other frequently used keys to more appropriate ones according to my keyboad.Is it possible? If yes, how can I do that? I have not seen anything in the documentation.
Thanks in advance.
The text was updated successfully, but these errors were encountered: