The VSCodeVim team prioritizes issues based on reaction count.
In INSERT MODE click ctrl+d don't add Selection To Next Find Match
just like VScode default setting
//vim config
"vim.easymotion": true,
"vim.incsearch": true,
"vim.useSystemClipboard": true,
"vim.useCtrlKeys": false,
"vim.hlsearch": true,
"vim.startInInsertMode": true,
"vim.insertModeKeyBindings": [
{
"before": [
"j",
"j"
],
"after": [
"<Esc>"
]
}
],
"vim.otherModesKeyBindingsNonRecursive": [
{
"before": [
"<leader>",
"d"
],
"after": [
"d",
"d"
]
},
{
"before": [
"<C-n>"
],
"after": [],
"commands": [
{
"command": ":nohl"
}
]
}
],
"vim.leader": "<space>",
"vim.handleKeys": {
"<C-a>": false,
"<C-f>": false,
"<C-d>": false
}
I think this is a duplicate of #1311. However what I find strange is that you have "vim.handleKeys": {"<C-d>": false} which is a workaround for this issue but results in #1467 nonetheless, hence not really solving the problem of multi-cursor functionality in insert mode.
The problem with implementing this is that in order to do a ctrl+d, vscode needs to select the word first.
However, for us, selecting a range necessarily puts us into visual mode (I think). It's fairly trivial to enable D-d in insert mode, but that would drop you into visual mode.
I'll try to find a solution, but it might be difficult.
This still doesn't work for me.
Without vim (as expected):

With vim (only adds selection to the whole word):

@binarious That's a bit different of an issue. Could you open up another issue for that?
I think this is a duplicate of #1311. However what I find strange is that you have
"vim.handleKeys": {"<C-d>": false}which is a workaround for this issue but results in #1467 nonetheless, hence not really solving the problem of multi-cursor functionality in insert mode.
this solution works if you have vim installed
Most helpful comment
This still doesn't work for me.
Without vim (as expected):

With vim (only adds selection to the whole word):
