Motion no longer works in the output window

[333fred]

Describe the bug

This may well be a VSCode 1.57.0 bug instead of a VSCodeVim bug, but I wouldn't know how to formulate the bug report to VSCode proper so I figured I'd open it here and let someone who knows the right words discuss with them.

Previously, I could use normal and visual mode motion keys in the output window. This was extremely useful for copying out baseline output into test files. On the latest updates of VSCode and the Vim extension, this is no longer working.

To Reproduce
Steps to reproduce the behavior:

1. Open a workspace that will trigger something to create output. For example, opening a git workspace will create an output window for the output of the git provider. Personally, this bug is breaking my workflow for test output from OmniSharp.
2. Open the output window, and select a non-empty log.
3. Click in the window to focus it and get a cursor.
4. Perform some kind of non-editing vim movement, such as j or V.

Expected behavior

The movement in step 4 happens.

Screenshots

This is the window I'm talking about, if output window isn't the right word:

Environment (please complete the following information):

• Extension (VsCodeVim) version: 1.57.0
• VSCode version: 1.21.2
• OS: Linux and Windows

Additional context

As I said, I think is probably a vscode 1.57.0 bug, but I don't really know the right words to describe the API that they would have broken here.

[J-Fields]

@333fred Can you try an older version of VSCode (and/or VSCodeVim) to help identify which is the culprit here?

[333fred]

I did try an older version of VSCodeVim, with no success. I can try an older version of vscode later today.

[333fred]

@J-Fields I tried with 1.56.2 just now, and yes it appears to be a 1.57 regression.

[333fred]

@J-Fields was this ever reported to the vscode team?