Please go to Settings -> Keymap -> Editor Actions and set up the shortcuts for Clone Caret Above and Clone Caret Below actions: Using Alt with the mouse click you can set the cursors in all places you need (please note that you may always change the shortcut in Settings -> Keymap -> Editor Actions -> Add or Remove Caret): It was the top voted editor feature in our tracker and we hope you will like it. Let me go through this short demo in more detail and show you all the tricks. Of course, they don't replace regex or other, just as a car doesn't replace a bike, nor a truck.If you, as me, often dream of being in several places at once you will like this new feature coming to RubyMine from IntelliJ platform side! Please welcome multiple cursors and selection that you can already try in the last EAP version: I think that multi-cursor operations are great, the reasons for that are well explained by the authors of kakoune and, probably more important, the success of such feature across different editors speaks for itself. In fact, it's hard to believe for me that there's still debate on whether it's a good idea or not, superior or not to regex or whatever, or that one should first master vi techniques. While I appreciate many things of neovim (I wouldn't be switching back to it otherwise!), I find that the lack of first-class support for multi-cursor selections and operations is a major drawback. I've been recently switching back to (neo)vim after a few years using sublime text and vs code.
I just wanted to add a comment, mostly to keep this thread alive. Looking through may give more ideas about what users expect from a multiplecursor feature and the current state of things. * mappings for actions like FindNext, GoBack (undo FindNext), SkipCurrent.
* convert search results into cursors (in a file or in a selection). * search for exact text if in Visual mode (both are currently working as expected in the plugin and have an option to toggle)
* search for the whole next word if in Normal mode Each cursor should paste it's own data (a part of that implemented in ). or for copy/paste, two scenarios are intuitive: 1) copy "something" using one cursor, create N cursors, paste that "something" into N locations 2) create N cursors, copy something, move cursors, paste. Maybe plugin authors have ideas about that, e.g. Maybe there are ways to implement it transparently to all the plugins, or maybe there could be a reason to expose some API, I just don't know at the moment. The reason why such mechanism is needed in vim-multiple-cursors is because the plugin is somewhat naive and its actions are observed by other plugins such as deoplete, neocomplete or YouCompleteMe and excessive (sometimes harmful) work is performed as a result. To me, it's probably issue number one right now (along with general instability and unpredictable behavior - if you press something beyond the plugin's prime, vim's gonna burst with errors corrupting text along the way).īut again, it depends on the core implementation details. I basically wanted to point out that it's a very huge bummer that completion menu cannot be used with current implementation of, while other editors do that (like VSCode).
That sounds reasonable, though the devil could be in the details. The only thing that makes sense to me: let the "primary cursor" operate the menu, and whatever choice is made there is duplicated at the other cursors Not saying it's a problem in vim, just pointing out gotchas in other editors. In VSCode though I remember there was a problem with conflicting keybindings (ctrl+click would follow the definition instead of placing a cursor). Perhaps also removing a cursor if an existing cursor was clicked.