[wonger_]

I used to want multicursor as well. But I heard a recommendation that multicursor is not "the vim way", and instead to use macros or regex search-and-replace or visual-block mode. That's worked for me.

Of course multicursor must be commonly requested for a reason. Just passing along some alternatives.

[ratorx]

I think multicursor vs macro is basically a case of whether the feedback is instant, rather than delayed.

Multicursor (in other editors) is a lot better, because you don’t have to think about which exact motion to use as much (since you can see it as you do them).

On the other hand, macros and vim motions are a lot more general, but require you to think about the exact motions a lot more ahead of time.

I think substitution (and command) previews (vs not having these features when substituting) is a good parallel to what multicursor adds over just macros.

[xigoi]

Doesn’t multicursor also require thinking about the exact motion, since if you do it wrong, there is no way to undo?

[ratorx]

I’m fairly sure VS Code supports undo whilst using multicursor? Why do you say that undo is not possible?

If it’s an inbuilt feature, the editor can definitely support undos.

[xigoi]

I meant undo for motions, not edits. I’m pretty sure Neovim does not have that. (There is <c-o>, but only for large motions.)