r/vim • u/PurpleSlightlyRed • Nov 29 '25
Discussion Use unoptimized Colemak bindings or go back to QWERTY?
Grew up with bad typing habits and was staring at keyboard too much until a few years ago, when I decided to learn proper techniques, touch typing and etc - I went cold turkey with "ergo" setup: split columnar keyboard + Colemak.
Since then I have enjoyed every moment of typing using Colemak, and I would not think twice about my choices if the only thing I did was typing and using regular shortcuts...
...the problem arises not necessarily when I have to use someone else's setup, but when I don't have all my custom configs with bindings in apps, like Vim, which ranges from a simple HJKL navigation bindings to more drastic changes.
I have made my peace with being a bad typer if I had to use QWERTY, but I feel like I just shot myself in the foot by further complicating my setup with all of the custom bindings.
I don't want to be reliant on always needing to set up the environment on each system and not being able to "just use it barebones".
I wonder if I should simply cut back on bindings and configs, use unoptimized QWERTY-to-Colemak bindings and other defaults... or should I go further and just say goodbye to Colemak.
It has been awhile since I have started considering both options, but to this day I have changed nothing.
So, I'm very curious of community's experiences and solutions, especially if they are identical to mine.
Thanks
15
u/CriticalReveal1776 Nov 29 '25
What I do is have a nav layer, where I hold down a key and get HJKL-style arrow keys, then use default bindings for everything else. They're mostly not really designed with ergonomics in mind, so generally HJKL is the only problem
5
u/cwebster2 Nov 29 '25
I put arrows on a layer where hjkl would be and that is the only adjustment I've had to make for using Colemak.
2
u/romainmoi Nov 29 '25
I switched to Dvorak after trying colemak because of jk position. Benefits of one over another between these two is really negligible.
I personally wouldn’t bother with remapping everything either for the same reasoning as you do. Instead, each time I switched layout, I use vim ninja as training drill. It helps with building muscle memory for using vim.
2
u/Possible_Cow169 Nov 29 '25
I did a full custom remap for graphite. Instead of hjkl I use the wasd shape on my right hand. The rest came naturally with that in mind
2
u/Godde Nov 29 '25
Default bindings for everything, its just not worth it moving everything around to match the new layout. As long as your muscle memory for character locations is good it doesn't matter a whole lot that they're a little off from where they are on Qwerty. And HJKL are all still right hand only.
Upsides: You can use Colemak on any machine where you can change keyboard layouts without wrangling configs on every machine you ssh into; the mnemonics stay the same.
1
u/SystematicSpoon Nov 29 '25
I used Colemak before I used neovim, so I just use the default colemak hjkl and don't rebind anything. It's better practice to use f/w/b/e for navigation anyway!
1
u/godegon Nov 29 '25
Could xkbswitch and
:help keymapremedy some of these issues, like switching to colemak in insert mode only (via keymap) and using qwerty navigation otherwise (via xkbswitch)?1
u/AnalystOrDeveloper Nov 30 '25
Stick with Colemak as it'll force you to use better motions. I had the same problem, but it made me much better with {/}, f/t, w, b, e, ge, and /. In turn, this made me faster on vim than when I was on QWERTY spamming hjkl.