Cmd+D loses multiple selections
See original GitHub issueIs this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
What happened: After a recent VSCodeVim update (since v0.10.12?), pressing Cmd+D sometimes loses multiple selections
What did you expect to happen: Selections should be maintained when using Cmd+D to select multiple occurrences
How to reproduce it (as minimally and precisely as possible):
- In normal mode, position the cursor within a word that is repeated within the current buffer
- Press
viw
to select the current word in visual mode - Press Cmd+D; another cursor is created at the next occurrence, and the status bar indicates that the editor is still in visual mode, however the selection is lost and the cursors are moved to one character after the ends of the words (preventing the ability to use
c
to replace both selected occurrences).
Environment: macOS
- Extension (VsCodeVim) version: 0.10.3
- VSCode version: 1.19.2
- OS version: 10.12.6
Issue Analytics
- State:
- Created 6 years ago
- Reactions:27
- Comments:27 (10 by maintainers)
Top Results From Across the Web
html - How to disable the drag selection on multi select without ...
I created a multiple select list box using the select tag as shown in the code below in Angular 5. <select multiple id="MySelect">...
Read more >The logic of multiple select - Autodesk Community - Fusion 360
The short answer to your question is: in most cases, you need CTRL/CMD when there is an active command preview. It's not 100%...
Read more >That command cannot be used on multiple selections - Office
Describes an issue that occurs when you try to copy nonadjacent cell or range selections.
Read more >Ctrl+Click multiple selection not working - Parallels Forums
I've swapped the ctrl and cmd keys for a Win 8.1 but as a result, I have lost the ability to select multiple...
Read more >Select multiple Clips with CMD key not working
CMD works with all other stuff. Just selecting multiple regions doesn't works as described. Help file: 'Select multiple items that are not ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am experiencing this problem today as well - but not intermittently, it happens every time the second selection is made.
me pressing cmd+d repeatedly on
@extend
☝️The one requirement for me to use any extension in vscode is that it doesn’t fuck with ctrl+d. I use it so much. And I have just been over so many issues and still can’t get it working. I got it selecting what it should in visual mode if I config to
true
.But this doesn’t help me, I need to be in insert mode and it doesn’t work in insert mode. And going back to insert mode removes the selection as well.
This is such a big issue that keeps getting posted over and over. Why not have a specific setting just for it that people can easily enable so they know what should happen. And then any reports of issues you know isn’t configuration (which is still unclear) so you know when there are real issues.
I can live withoug vim. I can’t live without an effective ctrl+d 😦
What we all want seems to be the default behavior which you say is by setting undefined… which you can’t do.