Vim: Remap of ["j", "j"] to "<Esc>" is no longer working

[gwintrob]

Describe the bug

I remap pressing "j" twice to "Esc" in insert mode.

    "vim.insertModeKeyBindings": [
        {
            "before": [
                "j",
                "j"
            ],
            "after": [
                "<Esc>"
            ]
        }
    ],

This has worked perfectly for a long time. Starting today, when I press "j" twice in insert mode, I end up with one "j" and the cursor at the prior character in normal mode.

To Reproduce

1. Add the insertModeKeyBindings setting above
2. Hit "i" to enter insert mode and type something like "test"
3. Hit "j" twice

Expected behavior

Screenshots

Here's a video. I updated "vim.debug.loggingLevelForConsole": "debug" but I'm not seeing anything in Output after restarting:

Environment (please complete the following information):

Extension version: 1.14.0
VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T17:07:18.473Z)
OS version: Darwin x64 19.4.0

Additional context

Thanks for such an important extension. I use it everyday!

[zerovolts]

This is also happening for me now when using jk/kj with v1.14.0 on Windows. It seems to occur every _other_ time I use the combo (by repeating jkijki...).

[botforge]

Yes! Same here! Definitely an issue with the latest update. Does anyone know how to install a rolled back version?

[bilalq]

Just ran into the same issue. You can workaround this by explicitly installing an older version of the extension either through the CLI or by searching for the extension in the IDE, hitting the gear icon, and selecting "Install Another Version".

1.13.1 is fine and 1.14.0 is where the issue was introduced.

[benlindsay]

Yep, I'm seeing the exact same thing. I recorded a video just to add to the context. I'm on a clean VSCode Insiders with no other extensions besides Vim, and I type "ijk" over and over, showing that it leaves behind a "j" every other time I do it.

And here's showing that it's fixed after reverting to the previous version:

[pak11273]

If you don't want anymore "punch you in your face" surprises like this happening in the future. You might want to

"extensions.autoUpdate": false,
"extensions.autoCheckUpdates": false

in your settings.json

[suhailibnnisar]

Hell No I even uninstalled vscode and deleted ~/Code folder to fix this.

[benjaminbenais]

Just ran into the same issue. You can workaround this by explicitly installing an older version of the extension either through the CLI or by searching for the extension in the IDE, hitting the gear icon, and selecting "Install Another Version".

1.13.1 is fine and 1.14.0 is where the issue was introduced.

Thanks! Installing 1.13.1 fixed the issue for me.

[ugirc]

Install 1.13.1 also works for me. Thanks!

[faustaleonardo]

Thank you 🕺

[gwintrob]

Woo hoo! Thanks @gergelyth, @J-Fields, and team.

[J-Fields]

This should be fixed in 1.14.1, which will be available momentarily. All credit goes to @gergelyth

[csuzdy]

I can confirm, 1.14.1 fixed the issue for me.