With `normalModeKeyBindings`, typing `< >` in Normal mode breaks keyboard input.

After adding any custom mapping with Ctrl in it (e.g. <C-n>) to normalModeKeyBindings (and/or normalModeKeyBindingsNonRecursive) and typing < > in Normal mode breaks keyboard input.

1. Add line "vim.normalModeKeyBindingsNonRecursive": [ { "before":["<C-n>"], "commands": [ ":nohl" ] } ] to your settings.json (example remapping from documentation).
2. Open any file, even empty.
3. Type < >.
4. Any further input will be directed into the status bar, to the left of Mode indicator. Even pressing <C-c> and/or <Esc> will only generate more text, but wont exit this... State.

Expected that command < > will be recognized as faulty and wrong, the Vim will leave "operator pending mode" and return to Normal mode. By the way, command > < behaves just like that, simply returning to Normal mode.

Example of a broken status line:

• Extension (VsCodeVim) version: 1.8.1
• VSCode version: 1.35.1
• OS: Windows 10 1903

There are more remapping in my settings, but the bug can be reproduced with only one line in settings.json. It's only caused by Ctrl based mappings, mapping single letters or letter sequences to Vim or VS Code commands does not trigger the bug, at least in my case.

Reproduce the issue using the normalModeKeyBindingsNonRecursive entry in settings.json and the documented Ctrl-n mapping, then trace the normal-mode keybinding and operator-pending handling. Done means < followed by a space and > returns to Normal mode without trapping subsequent input in the status bar, while the existing > < behavior remains intact.