Am I the only one who doesn't get the multi-cursor hype? Having said that I never used it, so maybe I'm missing out.
But actually it's more like defining a keyboard macro. It's very powerful and quicker and easier than a macro for a lot of tasks.
But I don't see another purpose for them; find-replace with regex support and macros only fail in rare cases where actual syntax parsing is needed.
But in vim it's not much slower to do:
/<search term>
cgn " change this this i just matched
. " find next occurance AND execute the change here too, i don't have to say "n ." because i used cgn above instead of something like cw
But i still end up relying on qq " stick a macro in q register
<complex edit sequence>
@q / @@
For more gnarly stuff :%s//<replacement>/gcThe advantage over search-and-replace is that you get to work with a nice, familiar language (the interactive commands you send to your editor) rather than using regex.