VSCodeVim
Graphical artifact when pressing space in insert mode (mac)
Type: Bug
Describe the bug When inserting text there is a visual artifact where the line entire drops down about 1/2 of the line hight and the cursor jumps back 2-3 characters every time I hit the space key.
To Reproduce
- Install version 1.17.0 or later of the vim extension in VSCode on Mac
- Hit
ito enter insert mode - Type a word and then press space
- For about 1 second, the line will drop down by about half of a line-height and the cursor will jump backward 2-3 characters.
A screen cast of this issue can be viewed here.
Note that this occurs even when I've disabled all other extensions, and this issue has occurred consistently since the release of 1.17.0. I've stayed on 1.16.0 since 1.17.0 was released but am getting annoyed as some of the bugs in 1.16.0 and would prefer to upgrade to the latest version, but this bug makes VSCode VIM almost unusable.
Extension version: 1.16.0 VS Code version: Code 1.78.2 (Universal) (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:44:45.204Z) OS version: Darwin x64 22.4.0 Modes: Sandboxed: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | 2, 2, 3 |
|Memory (System)|32.00GB (1.29GB free)| |Process Argv|--crash-reporter-id 0d1cb087-07c6-4eff-8f70-436ed3a22c66| |Screen Reader|no| |VM|0%|
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
2i9eh265:30646982
showlangstatbar:30737416
vsccsb:30705552
pythonms35:30701012
7ij38806:30736111
pythonfmttext:30731395
pythoncmv:30739700
fixhidewlkth:30730051
pythongtdpath:30739704
@josemanuelp Do you happen to have any insert mode keybindings ("vim.insertModeKeyBindings") in your VSCode settings? On further inspection, it seems this might be specific to insert mode keybindings, but wanted to get another confirmation.
For what it's worth, here's an updated screencast illustrating the issue, and that (for me) the issue is specific to insertModeKeyBindings
Yes, I did have it...
(when I used it, but I couldn't bear it, so I switched to Nvim, and I'm happy now, xD).