Theo Lemay

I think this is caused by bugs in the extmark-overlay PR.

Related: #389

Is the solution mentioned above not enough?

Please try with empty settings.json, init.vim, and all extensions disabled. I am unable to reproduce this.

Are you sure you are not sending ctrl-k to neovim yourself?? This plugin does nothing to bind ctrl-k.

> Insert mode is handled by vscode. The only time vscode communicates with the neovim instance during insert mode is when a command is executed due to a key sequence...

Duplicate of #968

I'm not sure if this is the best solution, but it is worth a try. The automation would come from some visual selection updated autocommand/event, if it exists. I wonder...

Check out this alternate solution! https://github.com/vscode-neovim/vscode-neovim/pull/886#issuecomment-1175189763

Check out this alternate solution! https://github.com/vscode-neovim/vscode-neovim/pull/886#issuecomment-1175189763