Bugvim1.0.1Darwin x64 18.0.01.31.0-insiderDescribe the bug
About two weeks ago I started frequently getting errors like "ModeHandler: error handling key=l. err=TypeError: Cannot read property 'position' of undefined." This appears in dialog in the lower-right of VS Code that I can dismiss, but it comes back frequently.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Don't display this error message.
{
"activationTimes": {
"startup": true,
"codeLoadingTime": 430,
"activateCallTime": 4,
"activateResolvedTime": 210,
"activationEvent": "*"
}
}
Easily reproducing when trying to go to mark which is unset yet.
E.g. 'a produces an error, but after ma it won't
Getting these kinds of errors all over the place now. Here's another one:

I'm on mobile so excuse brevity. The changelog is always a good place to take a look.
In v1.0.0, we now present errors as notification windows. These were previously outputted to console and not very discoverable. If you wish to continue living in bliss/ignorance of extension errors it's configurable. See the readme.
Vim: 1.0.2
Windows x64 10.0.16299
VSCode: 1.30.2
I received the <C-d> error but this has already been fixed I believe.
I now get, occasionally, when trying to use backspace:
ModeHandler: error handling key=<BS>. err=Error: Illegal argument: character must be non-negative.
Not sure exactly when this occurs, but it seems to be occurring when modifying whitespace before any characters (JSX source code).
Going out of insert mode and back in is a workaround.
I also have the same issue
ModeHandler: error handling key=<BS>. err=Error: Illegal argument: character must be non-negative.
When in insert mode of a CSS file and pressing backspace on the beginning of an empty line to try to delete this line.
when I want use `to skip the position that I not create the mark
then pop the error.
For example,normal mode。
click to `m

This error happens to me also. For me it is pretty simple to duplicate:

It seems a few different issues are being discussed here. For the "character must be non-negative" one, I created #3915 which is fixed by #3916.
Most helpful comment
This error happens to me also. For me it is pretty simple to duplicate: