| My bad, meant C-SPC. > What does your sequence of commands mean in English? This time I tested it to make sure that I say the right bindings: 1. Go to the beginning of the line (C-a)
2. Find the n'th column (n * C-s |)
3. Activate the mark (C-SPC)
4. Go to the next column (C-s |)
5. Kill the region (C-w)
6. Go to the column you want (m * C-s/C-r |)
7. Insert the region (C-y) > How natural is it to express? To me it is instinctive. > How much scripting and packaging does it require? None, these are all basic commands. > How much extra memorizing does it require? All you need to know is how to record a macro. > Yes, I am talking about interfaces, not software. I was talking about the interface that Emacs offers by default. But then you are comparing different apples to oranges? But even if we are comparing vim/kak the interface to Emacs' default interface, I still don't think the difference is that big. The main difference is that vim/kak are parts of the terminal workflow, while Emacs is a shell onto itself. > Multiple cursors give instant feedback, this is a big advantage over blindly shooting macros at your text. You have instant feedback while recording a macro too? You can even make it interactive, and insert a query into your macros to make it easier for you to distinguish between false-positives and the actual places you want to apply macros. |
But. Kakoune is still something bigger for me. It does take text editing to a new level and it does make it more efficient. It is similar to Emacs in the sense that both follow the sequence “select and apply an action”. But Kakoune has richer selection primitives and has actions that work on multiple selections at the same time; this can be done with macros, but it's by far less convenient.
In your example, you can record a macro and apply it to all the lines of a table. Will you have to do it for each line one by one? Can you say, “run the macro on each line of this paragraph”?
> You have instant feedback while recording a macro too?
Sure, but not on all the places where you're going to apply it at the same time. And your macro may not work correctly on some of the lines, you will not see it while recording it. With multiple selections you see it immediately and can undo the last action and try again.
Multiple selections stay there after you apply actions on them. After you apply something, you can see the result and slowly think of the thing to do next with them. With a macro, you will have to type in the whole sequence when you record the macro.
Macros can achieve the same things, but they require more mental effort and are harder to get used to. And when you're focused on your code, the mental effort it takes to used your editor matters.
In the same way, multiple selections are an improvement over Vim's tradition of shooting regexes at your text; for the same reasons: interactiveness and instant feedback.