Neovim :g commands getting error E488: Trailing characters

[sjsivert]

Describe the bug
g commands, and normal commands does not work. Even after enabling neovim and configurating

To Reproduce
Steps to reproduce the behavior:

1. Open any file
2. Write :g/#/d
3. See error "E488: Trailing characters"

Expected behavior

Expected all lines mathing # to be deleted

Screenshots

Environment (please complete the following information):

• Extension (VsCodeVim) version: v1.21.10
• VSCode version: 1.62.1
• OS: Linux x64 5.14.16-arch1-1

Additional context
Add any other context about the problem here.

[alexhwoods]

I get the same error just moving lines, .e.g. :5m10, also with neovim enabled.

• OS: macOS Big Sur
• VSCode version: 1.62.2
• Extension (VsCodeVim) version: v1.21.10

[zach-b]

Same here, with the same versions and OS as @alexhwoods

[liuxinge]

Same E488 here.

[WingDust]

+1

[tcd]

Any word on this?

[katuo0011]

I get the same error too

• OS: macOS Big Sur Version 11.4
• VSCode version: 1.62.3
• Extension (VsCodeVim) version: v1.21.10

[adinklotz]

We've heard from macOS and Linux, so chiming in with same on Windows:

• OS: Windows 10 build 19044
• VSCode version: 1.63.2
• Extension (vscodevim) version v1.21.10

[gotofritz]

This may well be related - #7207

Thanks for the report! I re-wrote most of the parsing from scratch recently - I'm sure lots of these little bugs have been introduced. :move is actually not yet implemented though (I plan on doing that soon; the recent re-write has made filling in these gaps in functionality easier), see #2472. The parser is throwing the wrong error here, should say the command isn't implemented.

Just a wild guess, but if :move hasn't been implemented yet, :norm and :g may also be WIP

[gotofritz]

And there are more:

:edit #7272
:ab #7243
#7058

...and so forth and so on. Looks like the developer has a lot of issues to deal with, wish I had time to help!

[J-Fields]

Should be fixed in 1.22.0

[dandenkijin]

it's baaaaaaaaack