Performing some actions via "vim command" dialog with neovim integration enabled causes vim extension to stop responding to keypresses

• Click thumbs-up 👍 on this issue if you want it!
• Click confused 😕 on this issue if not having it makes VSCodeVim unusable.

The VSCodeVim team prioritizes issues based on reaction count.

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report

Environment: Linux x86_64, Arch Linux, i3wm. All packages up to date.

• VSCode Version: 1.8.1
• VsCodeVim Version: 0.10.4
• OS: Linux

What happened: Performing some actions via "vim command" (pressing :) cause the vim extension to stop working; afterward, vscode shortcuts (like ctrl+p) work fine, but vim movements are ignored in the window.

This only happens with neovim integration enabled; disabling it resolves the issue.

This began happening this morning; i'm assuming it's because the plugin updated in the background or the like. I'm unsure how to determine when vscode updated an extension, or what the previous version i was on was.

What did you expect to happen: using the "vim command" dialog should not cause issues

How to reproduce it:

• :100 to jump to line 100 causes the issue
• :s/something/otherthing/g causes the issue
• :w does not cause the issue

Notably, the action is ignored. Say when typing :100 the dialog is dismissed, but the cursor does not jump. Same for a find/replace. No messages are logged in the web console.

Let me know if i can provide any other information. Thank you!

Start by reproducing the failure in the vim command dialog with neovim integration enabled, using the listed :100 and :s/something/otherthing/g cases and the Linux environment details. Compare those with :w and with neovim disabled; done means the command executes and vim keypresses continue working afterward.