-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remap of ["j", "j"] to "<Esc>" is no longer working #4787
Comments
This is also happening for me now when using |
Yes! Same here! Definitely an issue with the latest update. Does anyone know how to install a rolled back version? |
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. |
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: |
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 |
Hell No I even uninstalled vscode and deleted |
Thanks! Installing 1.13.1 fixed the issue for me. |
Install 1.13.1 also works for me. Thanks! |
Thank you 🕺 |
Fix insert mode key remaps leaving characters behind. This happened due to the new historyTracker optimizations, where we don't add the new characters one by one to history, but rather just the first one and then the rest at the end. Fixes #4787
Woo hoo! Thanks @gergelyth, @J-Fields, and team. |
This should be fixed in |
I can confirm, 1.14.1 fixed the issue for me. |
Fix insert mode key remaps leaving characters behind. This happened due to the new historyTracker optimizations, where we don't add the new characters one by one to history, but rather just the first one and then the rest at the end. Fixes VSCodeVim#4787
Describe the bug
I remap pressing "j" twice to "Esc" in insert mode.
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
insertModeKeyBindings
setting aboveExpected 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!
The text was updated successfully, but these errors were encountered: