-
Notifications
You must be signed in to change notification settings - Fork 50
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
use the home row for moving around #9
Comments
You suggest NEIO for HJKL instead of HNEI? It seems like that would make more sense, but I think I wouldn't prefer it because my accuracy with little finger is worse than with ring finger. Additionally, I prefer keeping the physical position of those actions to avoid further complicating required brain wiring. Should we make vim-colemak mappings more flexible? |
@jooize precisely. It does for sure require a different habit than the QWERTY keyboard, but isn't that the point anyway? Since we are on Colemak, we don't suffer from having the I'd love to have that option so I don't have to maintain my fork. I'd love to even see it defaulting to |
+1 for this |
HNEI makes the most sense ergonomically. The majority of the load is placed on the two strongest fingers of the hand -- and I believe they have separate tendons as well, unlike what would occur if one were to use NEIO instead. Inter-line movement (down and up) is far more common than intra-line movement (left and right). Especially with One "compromise" is:
...but I'm not sure that it's worth the slight reduction in muscle memory. |
The reason why Vim moves the home row one key to the left is that on qwerty the rightmost key in the home row is the semi-column. That's not the case in Colemak though, so why not fix it?
I use Kinesis keyboard, so it makes much more sense for me to use the home row as it's intended, so a while back I forked this repo and move the keys. Is this something you'd consider?
My fork is located at https://github.com/kalbasit/vim-colemak (see README).
The text was updated successfully, but these errors were encountered: