4 ms·
What version of VsVim are you using? There was a bug with this exact behavior in 1.1 (and possibly 1.1.1). I got it fixed for the 1.2 release which is the cur
by jaredpar 15y ago
What version of VsVim are you using? There was a bug with this exact behavior in 1.1 (and possibly 1.1.1). I got it fixed for the 1.2 release which is the current version in the Visual Studio gallery.
Bug Details: https://github.com/jaredpar/VsVim/issues/672 https://github.com/jaredpar/VsVim/issues/672