3 ms·
Why multiple cursors don't work (for me, of course): 1) I'm limited to what I can see. I can't see that a command does not generalize unless it's on the screen
by falcolas 9y ago
Why multiple cursors don't work (for me, of course):
1) I'm limited to what I can see. I can't see that a command does not generalize unless it's on the screen. Most files I work on take up more than the one screen I'm on.
2) Multiple cursors tend to have really limited flexibility - if it can't be done easily with the available movement keys, often times it can't be done. Macros, on the other hand, can easily move non-contiguously.
Yeah, macros do require a bit of extra thought around "how do I program the text editor to do what I want", but they usually do the right thing. It helps that macros are easy to record and use in vim, and that a macro can call another macro.
Of course, I have used multiple cursors before, but usually only in data files which follow strict columnar formats.
- mickronome 9y agoIsn't what you are describing simply implementation deficiencies of current multi-cursor implementations ? Conceptually, multiple cursors are nothing but a partial visualisation of a macro functionality.
- trishume 9y agoI don't encounter either problem: 1) If I'm editing things that don't fit on one screen, I'll scroll and check them all after I'm done. This is no slower than the scrolling needed during the step of applying a macro everywhere and checking it. And I at least get feedback from one page while composing my edits, with macros I get none. 2) I use multiple cursors with Vintageous in Sublime, so I get most of the power of vim macros, but with multiple cursors instead.