Add selection to next find match misbehaves

BUG REPORT: Add selection to next find match misbehaves when vim is enabled

What happened:
Add selection to next find match does not behaves as expected on Linux
when the vim extension is enabled.
It selects correctly the word under the cursor, but jumps to the
end of the word. Calling the command once again select the
seconds word, but the command does nothing the third time is is called.
The behavior is the same in both normal and insert modes.

What did you expect to happen:
Add selection to next find match should keep selecting words.

How to reproduce it (as minimally and precisely as possible):

Calling the function through the commands directly or through a keyboard
shortcut gives the same result. Here is a small screencast.

Environment:

• Extension Name: vim
• Extension Version: 0.11.2
• OS Version: Linux x64 4.15.6-1-ARCH (ArchLinux)
• VSCode version: 1.21.0

I could reproduce the issue on a macOS machine too.

Start by reproducing the “Add selection to next find match” command in VS Code with the Vim extension enabled, in both normal and insert modes. Trace how repeated commands update the selection and cursor position; done means successive invocations select successive matches without jumping to the word end or stopping.