colemak disperses hjkl, so it would be difficult to navigate a file with colemak keyboard layout.
A few references from here regarding using Kakoune with alternative layouts:
I’ve been using kakoune with colemak for 2 years now. Check out my mappings: kakoune-config/colemak.kak at master · JJK96/kakoune-config · GitHub
I’ve also been using Kakoune with Colemak-DH for a long time. At first I was using the default bindings to see if I could get used to them. I did, but after a while it started to get really uncomfortable because of the
hjkl, so a few weeks ago I decided to remap every one of my bindings and even change some of non-
hjkl bindings too to try to get them as comfortable as possible in every way. Since I was already going out of my way to learn a new more efficient layout like Colemak-DH, might as well learn a new more efficient layout for modal editing. (Yeah, I didn’t have anything better to do)
hnei on vanilla Colemak,
hjkl on qwerty) the directional movement keys, and
uio on qwerty) the word movement keys (
bwe). This makes the right hand responsible for all movement and I find them really intuitive.
Then I had to cycle some other keys to fit all those changes in. Like e.g.
m on both Colemak and qwerty) is my
i (insert mode) now.
I’ve been really happy with these changes and my discomfort with
hjkl is gone.
Only problem after that was, if the default Kakoune bindings made going back to just Vim hard, these mappings made the whole TUI
hjkl ecosystem harder haha. I’ve been remapping only the programs I use the most to use
hjkl and then I fall back to a layer on KMonad that maps them to the arrow keys instead. It’s been working good enough for me that way.
I’d post my config but right now it’s a big mess with lots of repeated mappings for all modes. I haven’t gotten around to organizing it yet.