16 ms·
Counterpoint: I have used Kakoune for a year now, immediately following sixteen years of heavy vim use. I find Kakoune far more intuitive than vim, because the
by jasone 6y ago
Counterpoint: I have used Kakoune for a year now, immediately following sixteen years of heavy vim use. I find Kakoune far more intuitive than vim, because the feature set composes so well. Within the first few weeks I understood the command set well enough to combine features to solve editing problems I would have had to look up solutions to if using vim.
Regarding the worry of visual distraction of selections slowing down editing, I found the opposite to be the case as I became more fluent with Kakoune. Motions modify the selection, and it is quite common for the selection to serendipitously contain what I want to modify. Constantly visible selection(s) lead me to implicitly take advantage of motion and use fewer keystrokes.
Regarding multiple selections outside the visible window, you are right that there's no visual feedback for those selections, which is a degraded experience compared to when all selections are visible. But that's no worse than the experience of a global search/replace in vim. You are arguing that in an edge case, Kakoune is no better than vim, which doesn't seem like a meaningful detraction.
- chongli 6y agovisual distraction of selections slowing down editing This is going to be a dealbreaker because having things moving around in one's peripheral vision is extremely distracting for a lot of people, including me. When I am typing I want my focus to be on the one place where I'm inserting text. I don't want to see all these other cursors moving around. But that's no worse than the experience of a global search/replace in vim I rarely ever use the default global search/replace in vim. Most of the time I search with / and then perform an edit there, and then use n.n.n.nn.nnn. to repeat the changes in the places I want.