The VSCodeVim team prioritizes issues based on reaction count.
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Environment:
What happened:
Bug/error when completing go code
for<tab>
gives me :
for index := 0; index < count; index++ {
}
with multiple cursors around "index"
pressing "backspace", to change value of "index" gives me :
for ex < count; index++ {
}
What did you expect to happen:
changing the index value to something I want. If I put VSCodeVim off, everything is ok.
How to reproduce it:
Ensure Plugings :
I'm not sure if it's related to VSCodeVim or go snippets. Again, if I turn VSCodeVim off, everything is ok.
I believe one workaround for this currently is by using <ctrl-backspace> instead of backspace to delete.

Has there been any update on this issue? As shown in the gif, this problem still persists to this day. Multiple dupes have been closed, but the sole solution as of yet still seems to be the workaround of using <del> or <ctrl-backspace>.
I can reproduce the above problem, the above temporary solution is also valid.
I can reproduce the problem too. Currently on Version 1.40.2
Most helpful comment
I believe one workaround for this currently is by using
<ctrl-backspace>instead of backspace to delete.