Vim: Undo broken with new VS Code

Apologies for my slowness in responding to this issue; I’ve been quite busy with other things recently.

This should be fixed in v1.25.1. If you’re still experiencing this issue, please leave a comment letting me know. If there’s some other misbehavior related to undo, please file a new ticket.

When mapping the u to vscode’s Undo and <Ctrl-r> to vscode’s Redo in settings.json it works for me again.

 "vim.normalModeKeyBindingsNonRecursive": [
    {
      "before": [
        "u"
      ],
      "commands": [
        "undo"
      ]
    },
    {
      "before": [
        "c-r"
      ],
      "commands": [
        "redo"
      ]
    }
  ],

Still broken then… to summarize

Solution 1.

• https://github.com/VSCodeVim/Vim/issues/8157#issuecomment-1426704638
• Breaks the macro behaviour in vim mode as detailed this comment

    "vim.normalModeKeyBindingsNonRecursive": [
        // FIX https://github.com/VSCodeVim/Vim/issues/8157#issuecomment-1426704638
        // Wait for new release, else we should migrate to using vscode-neovim extension
        { "before": [ "u" ], "commands": [ "undo" ] },
        { "before": [ "c-r" ], "commands": [ "redo" ] }
    ],

Solution 2.

• Install nvim server and vscode-neovim

Solution 3.

• Downgrade to VSCode to 1.72.2

Solution 4.

• Fix the bug… ❣️
• Please read through the comments and see if you can contribute to that discussion

Until this issue is resolved, VSCode undo, redo can be temporarily set to Vim key bindings.

"vim.normalModeKeyBindingsNonRecursive": [
    // Undo & Redo
    { "before": ["u"], "commands": ["undo"] },
    { "before": ["c-r"], "commands": ["redo"] }
  ],

@alecthomas Don’t comment on GitHub issues with “Same” or “+1”. It’s rude, unhelpful, and spams everyone who is following the issue.

Right, better let the issue disappear in the ether of obscurity, or get automatically closed as stale. Giving the maintainers a nudge that the issue affects a lot of people is clearly a step in a wrong direction 😛

Use the nvim extension. Seems this project isn’t being maintained anymore.

@igniscyan This project clearly is being maintained - @J-Fields started looking into the issue 5 days ago.

Undo after saving the file or even before saving it doesn’t work for me as it used to do before the bug. VS Code 1.74.2

https://user-images.githubusercontent.com/55108505/210176104-2439956b-8a36-4d2e-9baa-faa31de313cb.mp4

@J-Fields thank you for letting me unsubscribe from this embarrassing whine-fest 😜

@alecthomas Don’t comment on GitHub issues with “Same” or “+1”. It’s rude, unhelpful, and spams everyone who is following the issue.

i think we have discovered the hardest engineering problem known to man

Please stop with the annoying +1 and “same issue” posts. Just thumb up the OP so that we can stay subscribed to this thread without reading dumb me-too posts

@t-var-s can’t find the comment that fixed this, but just try this:

  "vim.normalModeKeyBindingsNonRecursive": [
    {
      "before": ["u"],
      "commands": ["undo"]
    },
    {
      "before": ["c-r"],
      "commands": ["redo"]
    }
  ],

Thanks @J-Fields, I really appreciate the effort that you’ve put into this extension, it’s amazing.

@alecthomas Don’t comment on GitHub issues with “Same” or “+1”. It’s rude, unhelpful, and spams everyone who is following the issue.

This has been said upwards of 10 times on this thread. This is equally as useful as a +1 comment, pings everyone, and is intentionally contentious.

This is killing me.

Use the nvim extension. Seems this project isn’t being maintained anymore.

This is killing me.

Please stop with the annoying +1 and “same issue” posts. Just thumb up the OP so that we can stay subscribed to this thread without reading dumb me-too posts

Not trying to stir any hostilities here, but having some sort of an acknowlegment from maintainers that they are aware this is an issue and are working (at their own pace!) towards resolving it would probably help to put people at ease and reduce amount of “me too” here.

Same here.

I give up. I uninstalled the vim extension.

Still broken for me in version 1.26.0

You will also note that @J-Fields is working on a fix - https://github.com/VSCodeVim/Vim/pull/8249

So everyone else be patient

@alecthomas Don’t comment on GitHub issues with “Same” or “+1”. It’s rude, unhelpful, and spams everyone who is following the issue.

This comment is not useful.

When I press u, vscode undo to the latest change, and if press u again nothing happend.

saaame

Same here

sporadically maintained open source project

@lperson I’ve pointed this out to others - but this has been an amazingly well maintained project. It currently stands at 4,085 closed issues. That’s phenomenal. I think it has reduced down to just one developer working on it.

So if this is sporadically maintained, all open source is sporadically maintained.

Either:

1. Have patience
2. Use the work-around
3. Fork it
4. Use something else

But don’t go around insulting the project owners.

That’s not an insult. It’s a fact.

+1

Please stop with the annoying +1 and “same issue” posts. Just thumb up the OP so that we can stay subscribed to this thread without reading dumb me-too posts

Not trying to stir any hostilities here, but having some sort of an acknowlegment from maintainers that they are aware this is an issue and are working (at their own pace!) towards resolving it would probably help to put people at ease and reduce amount of “me too” here.

Same issue here, latest update broke things again

‘sporadic’ is an opinion

I know this is a very annoying issue, and I honestly tried Neovim VSCode, but I still came back to this because this project has been just good enough for me, and after I tried the temporal fix I’m quite happy, it’s not perfect but it revives my previous workflow.

Let’s try to be patient with the people maintaining this repository… obviously this is something completely non-intentional, and stuff happens… @J-Fields happy to contribute in any way possible, even just being a rubber duck or taking a look at specific parts of code

That’s enough for me; I am downgrading to 1.72.2 or 1.73, whichever works. It is such a shame that Microsoft doesn’t get a chance to fix it for such a long time. This is like the most basic text editor operation in the, perhaps, most widely used vscode extension.

UPD: I confirm it works in 1.73.1

@huyz I switched to another editor (Helix), not because this is a temporary issue, but because it made me realize that modal editing is an afterthought in VS Code (despite this extension being awesome). And these issues will keep appearing without being a priority for VS Code.

But that’s just me (modal editing is the most important part of my workflow). I’m sure downgrading is just fine for most people, as you mentioned.

https://github.com/VSCodeVim/Vim/issues/8157#issuecomment-1426704638

That works, but the native undo only undoes one time of the macro. Example:

+1, unusable VSCodeVim.

+1 also keeps the issue alive - emojis do not IIRC

same here vscodevim: v1.24.3 Visual Studio Code: 1.75.0 OS: MacOS 13.2 (22D49)

I am using VS Code 1.75.0 and still encounter this problem. I downgraded the VsCodeVim version to 1.1.0 to fix it for now.

so is this gonna be addressed?

The issues #8200 and #8201 seem to have appeared at the same time as this one. Is someone else affected by them? Has someone been able to reproduce the issue starting from a clean VS Code configuration? I’m trying, but with no success so far.

@J-Fields I’m still having the issue. This is my settings.json:

{
    "vim.vimrc.enable": true,
    "files.autoSave": "onFocusChange",
    "javascript.format.semicolons": "insert",
    "editor.rulers": [
        80,
        100
    ],
    "eslint.alwaysShowStatus": true,
    "eslint.format.enable": true,
    "eslint.lintTask.enable": true,
    "editor.fontFamily": "'JetBrains Mono', 'Droid Sans Mono', 'monospace', monospace, 'Droid Sans Fallback'",
    "editor.fontLigatures": true,
    "editor.fontWeight": 600,
    "vim.hlsearch": true,
    "vim.timeout": 0,
    "vim.normalModeKeyBindingsNonRecursive": [
        {
            "before": [
                "gq"
            ],
            "commands": [
                "editor.action.formatSelection",
            ],
        }
    ],
    "python.linting.pylintEnabled": true,
    "editor.minimap.enabled": false,
    "workbench.tree.indent": 20,
    "workbench.list.horizontalScrolling": true,
    "gitlens.fileAnnotations.command": "blame",
    "gitlens.currentLine.enabled": false,
    "gitlens.currentLine.pullRequests.enabled": false,
    "gitlens.currentLine.scrollable": false,
    "gitlens.codeLens.authors.enabled": false,
    "gitlens.codeLens.recentChange.enabled": false,
    "gitlens.codeLens.enabled": false,
    "git.autofetch": "all",
    "git.inputValidationSubjectLength": 72,
    "typescript.updateImportsOnFileMove.enabled": "always",
    "workbench.editor.wrapTabs": true,
    "window.openFilesInNewWindow": "on",
    "editor.suggestSelection": "first",
    "vsintellicode.modify.editor.suggestSelection": "automaticallyOverrodeDefaultValue",
    "files.exclude": {
        "**/.classpath": true,
        "**/.project": true,
        "**/.settings": true,
        "**/.factorypath": true
    },
    "terminal.integrated.scrollback": 10000,
    "[typescript]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "gitlens.advanced.messages": {
        "suppressCreatePullRequestPrompt": true
    },
    "window.openFoldersInNewWindow": "on",
    "[html]": {
        "editor.defaultFormatter": "vscode.html-language-features"
    },
    "javascript.updateImportsOnFileMove.enabled": "always",
    "workbench.colorTheme": "Default Light+",
    "cSpell.userWords": [
        "fdescribe",
        "testid",
        "upsert",
        "upserted"
    ],
    "cSpell.ignoreRegExpList": [
        "/from\\s+(['\\\"]).*\\1/"
    ],
    "editor.inlineSuggest.enabled": true,
    "editor.bracketPairColorization.independentColorPoolPerBracketType": true,
    "[scss]": {
        "editor.defaultFormatter": "sibiraj-s.vscode-scss-formatter"
    },
    "outline.showVariables": false,
    "editor.cursorBlinking": "smooth",
    "javascript.inlayHints.enumMemberValues.enabled": true,
    "javascript.inlayHints.parameterNames.enabled": "literals",
    "typescript.inlayHints.parameterNames.enabled": "literals",
    "editor.foldingImportsByDefault": true,
    "[vue]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "workbench.editor.enablePreview": false,
    "typescript.preferences.quoteStyle": "single",
    "javascript.preferences.importModuleSpecifier": "project-relative",
    "diffEditor.ignoreTrimWhitespace": false,
    "editor.defaultFormatter": "esbenp.prettier-vscode",
    "terminal.integrated.allowChords": false,
    "window.customMenuBarAltFocus": false,
    "window.enableMenuBarMnemonics": false,
    "vim.handleKeys": {
        "<C-d>": true,
        "<C-s>": false,
        "<C-z>": false,
        "<C-f>": false
    },
    "vim.leader": "Ñ",
    "vim.matchpairs": "(:),{:},[:],<:>,\":\",/*:*/",
    "vim.replaceWithRegister": true,
    "vim.visualstar": true,
    "jest.autoRun": "off",
    "gitlens.advanced.fileHistoryFollowsRenames": true,
    "editor.stickyScroll.enabled": true
}

Thank you for the fix 👍

Made an extension build with that line commented out: vim-1.24.3-test-undo-issue.vsix.zip from (https://github.com/homburg/Vim-1/pull/1/files)

I can’t reproduce the issue with this build. Curious to see how it works for others.

Obviously would need a real fix other than just removing that feature.

So simplifying my earlier bug report:

• yy
• p
• u - this doesn’t work.

Here is the debug log for this:

ModeHandler: debug: handleKeyEvent('y') took 1ms
ModeHandler: debug: handling key=y.
Remapper: debug: trying to find matching remap. keys=y,y. mode=Normal. keybindings=normalModeKeyBindingsMap.
Remapper: verbose: key=y,y. keySlice=yy.
Remapper: debug: normalModeKeyBindingsMap. potential remap broken. resending keys without allowing a potential remap on first key. keys=y,y
ModeHandler: debug: handling key=y.
Remapper: debug: trying to find matching remap. keys=y. mode=Normal. keybindings=normalModeKeyBindingsMap.
ModeHandler: debug: handleKeyEvent('y') took 3ms
ModeHandler: debug: handling key=y.
Remapper: debug: trying to find matching remap. keys=y. mode=Normal. keybindings=operatorPendingModeKeyBindingsMap.
ModeHandler: debug: handleKeyEvent('y') took 4ms
ModeHandler: debug: handleKeyEvent('y') took 9ms
ModeHandler: debug: handling key=p.
Remapper: debug: trying to find matching remap. keys=p. mode=Normal. keybindings=normalModeKeyBindingsMap.
Transformer: debug: Adding Transformation {"type":"moveCursor","diff":{"type":0,"line":21,"character":8},"cursorIndex":0}
Transformer: debug: Adding Transformation {"type":"replaceText","range":[{"line":20,"character":68},{"line":20,"character":68}],"text":"\n        captureException(`Failed to start server. ${error.message}`)"}
ModeHandler: debug: Selections: Adding Selection Change to be Ignored! (total: 1) Hash: [21, 8; 21, 8], Selections: [21, 8], [21, 8]
ModeHandler: debug: handleKeyEvent('p') took 18ms
Extension Startup: debug: Selections: Ignoring selection: [21, 8; 21, 8], Count left: 0
ModeHandler: debug: handling key=u.
Remapper: debug: trying to find matching remap. keys=u. mode=Normal. keybindings=normalModeKeyBindingsMap.
ModeHandler: debug: handleKeyEvent('u') took 1ms

If I close and restart VSCode it does briefly work (I don’t know at what point it stops):

ModeHandler: debug: handling key=y.
Remapper: debug: trying to find matching remap. keys=y. mode=Normal. keybindings=normalModeKeyBindingsMap.
Remapper: debug: normalModeKeyBindingsMap. potential remap found. waiting for other key or timeout to finish.
ModeHandler: debug: handleKeyEvent('y') took 2ms
ModeHandler: debug: handling key=y.
Remapper: debug: trying to find matching remap. keys=y,y. mode=Normal. keybindings=normalModeKeyBindingsMap.
Remapper: verbose: key=y,y. keySlice=yy.
Remapper: debug: normalModeKeyBindingsMap. potential remap broken. resending keys without allowing a potential remap on first key. keys=y,y
ModeHandler: debug: handling key=y.
Remapper: debug: trying to find matching remap. keys=y. mode=Normal. keybindings=normalModeKeyBindingsMap.
ModeHandler: debug: handleKeyEvent('y') took 3ms
ModeHandler: debug: handling key=y.
Remapper: debug: trying to find matching remap. keys=y. mode=Normal. keybindings=operatorPendingModeKeyBindingsMap.
ModeHandler: debug: handleKeyEvent('y') took 5ms
ModeHandler: debug: handleKeyEvent('y') took 10ms
ModeHandler: debug: handling key=p.
Remapper: debug: trying to find matching remap. keys=p. mode=Normal. keybindings=normalModeKeyBindingsMap.
Transformer: debug: Adding Transformation {"type":"moveCursor","diff":{"type":0,"line":21,"character":8},"cursorIndex":0}
Transformer: debug: Adding Transformation {"type":"replaceText","range":[{"line":20,"character":68},{"line":20,"character":68}],"text":"\n        captureException(`Failed to start server. ${error.message}`)"}
HistoryTracker: debug: Set nextStepStartPosition to [20, 27]
HistoryTracker: debug: Finished history step with 1 change(s)
ModeHandler: debug: Selections: Adding Selection Change to be Ignored! (total: 1) Hash: [21, 8; 21, 8], Selections: [21, 8], [21, 8]
ModeHandler: debug: handleKeyEvent('p') took 35ms
Extension Startup: debug: Selections: Ignoring selection: [21, 8; 21, 8], Count left: 0
ModeHandler: debug: handling key=u.
Remapper: debug: trying to find matching remap. keys=u. mode=Normal. keybindings=normalModeKeyBindingsMap.
ModeHandler: debug: Selections: Adding Selection Change to be Ignored! (total: 1) Hash: [20, 27; 20, 27], Selections: [20, 27], [20, 27]
ModeHandler: debug: handleKeyEvent('u') took 19ms
Extension Startup: debug: Selections: Ignoring selection: [20, 27; 20, 27], Count left: 0

Here’s the diff (Vim still does diffs better than VSCode 😉):

Two critical logs that appear in the working version but not in the failing version:

HistoryTracker: debug: Set nextStepStartPosition to [20, 27]
HistoryTracker: debug: Finished history step with 1 change(s)

Not sure about this rest…

For any people interested in switching to VSCode Neovim, it seems to be fairly painless.

I have tested out the extension and it is pretty nice. Has more moving parts, a bit weird and requires some getting used to, but overall it does the job and comes with more flexibility in terms of doing things within init.lua or init.nvim.

It does require having neovim installed on your host, but I rely on it a lot anyways, so that is not a big issue for me.

As always, your experience may vary.

Changes necessary to make it work: https://github.com/ddnomad/dotfiles/commit/d060fb7d3d66c682e729695a954ea0bb3f956593

@ddnomad I am only on MacOS and still have the issue since the update

We’re all software engineers. Can we put up a PR to fix this rather than piling on with complaints?

I haven’t had time to dig into the code but I found a PR that touched registers from late last year. It shipped in 1.24.3. That’s probably where I’d start looking.

We need one of the maintainer’s eyes on the PR for it to have any effect, any sort of acknowledgement would be good here.

Seeing mixed messages here of it working and not working. It’s intermittent - sometimes it works, sometimes it doesn’t. It’s almost something is happening upon save that is sometimes erasing history. Seems to be completely random - I’ve typed and re-typed the same text over and over again, and it is about 50/50 chance of remembering history after a save.

(https://github.com/VSCodeVim/Vim/issues/8157#issuecomment-1426704638)

This comment worked for me 🍻 Cheers mate

This isn’t really a solution. It’s just opting to use vscode’s native undo rather than the undo tree that the plug-in is supposed to have.

I tried debugging on the extension today, and I seemed to get a lot of history resets from this line: https://github.com/VSCodeVim/Vim/blob/e7075ad72e5b31b980ab52e9881b2b6a7b3bd673/extensionBase.ts#L635

Just from u-presses

Eg. call trace

new UndoStack (/Users/thomas/src/github.com/VSCodeVim/vim/src/history/historyTracker.ts:238:12)
    at new HistoryTracker (/Users/thomas/src/github.com/VSCodeVim/vim/src/history/historyTracker.ts:417:4)
    at new VimState (/Users/thomas/src/github.com/VSCodeVim/vim/src/state/vimState.ts:336:2)
    at new ModeHandler (/Users/thomas/src/github.com/VSCodeVim/vim/out/extension.js:63348:25)
    at Function.create (/Users/thomas/src/github.com/VSCodeVim/vim/out/extension.js:63314:29)
    at ModeHandlerMapImpl.getOrCreate (/Users/thomas/src/github.com/VSCodeVim/vim/src/mode/modeHandlerMap.ts:40:44)
    at getAndUpdateModeHandler (/Users/thomas/src/github.com/VSCodeVim/vim/extensionBase.ts:47:23)
    at /Users/thomas/src/github.com/VSCodeVim/vim/extensionBase.ts:264:5
    at Queue.start (/Users/thomas/src/github.com/VSCodeVim/vim/node_modules/queue/index.js:145:1)
    at Queue.<computed> [as push] (/Users/thomas/src/github.com/VSCodeVim/vim/node_modules/queue/index.js:59:1)
    at TaskQueue.enqueueTask (/Users/thomas/src/github.com/VSCodeVim/vim/out/extension.js:66815:24)
    at /Users/thomas/src/github.com/VSCodeVim/vim/extensionBase.ts:260:10

I am running vscode 1.75.1, haven’t tried comparing with an older vscode version

Thank you for the reproducing example, @ianchanning. I am able to cause this bug consistently with your method using vscode 1.75.1 and vim-extension v1.24.3.

However, I’m not able to reproduce this with OSS vscode built from source on tag 1.75.1 and only installing vscode-vim v1.24.3 via vsix. No problem undoing whatsoever.

I switched to use the VSCode NeoVim plugin. Pretty straightforward. Also, happy to pair program with literally anyone in this forum to see if we can find the root cause for this, I’d love to jump back to this project, the plugin is really unusable without this

EDIT: This comment solved it all https://github.com/VSCodeVim/Vim/issues/8157#issuecomment-1426704638 I’m now back to this plugin

I’ve found the debug statements now. You need to open up the literal Electron/Chrome Developer Tools within VSCode via Help > Toggle Developer Tools

It’s the HistoryTracker logs we’re interested in.

+1 this is insanely annoying

same issue. Quite strange since I’ve been using the same version for some time now

Strangely I just started experiencing this today, though presumably I have been on 1.75.0 since it released. Downgrading to 1.72.2 as someone above recommended seems to fix it.

same here and the . repeat function is also broken

It seems this issue is fixed now, at least in my VS Code 1.74.2.

Version: 1.74.2 (Universal) Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161 Date: 2022-12-20T10:26:09.430Z Electron: 19.1.8 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin arm64 22.3.0 Sandboxed: No

@marchbox are you able to undo changes with “u” after saving a file? I can still reproduce that issue with 1.74.2. which may be related to this. The last version where that worked for me is 1.72.2, see #8188.

Thank you, but I can’t see it in the extensions repository of vscode. Have you published it?

There’s been 2 new versions released recently, I can see both of them in VSCode so they have been released (checkout the version history on the VSCodeVim extension page here).

In VSCode you can also check the versions by right clicking on the extension -> click Install Another Version and see the available versions; if you don’t see them you might need to make sure VSCode is updated or maybe restart it? Or connect to the internet? smile shrug

I have already done everything you suggested except for first upgrading to the latest vscode and then checking, perhaps, this is the reason I couldn’t see the new version. 😃

I am seeing this issue as well.

VSCodeVim Version: v1.24.3

VSCode Version: Version: 1.75.1 Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf Date: 2023-02-08T21:35:30.018Z Electron: 19.1.9 Chromium: 102.0.5005.194 Node.js: 16.14.2 V8: 10.2.154.23-electron.0 OS: Linux x64 6.1.11-200.fc37.x86_64 Sandboxed: No

Use the nvim extension. Seems this project isn’t being maintained anymore.

@igniscyan This project clearly is being maintained - @J-Fields started looking into the issue 5 days ago.

Didn’t see. It’s been marked as upstream so it’s already looked into.

I’m experimenting with the neovim extension. After installing neovim it seems to just work. It was NOT necessary to install neovim in my dev container, which is also great news. It seems to run locally. 🤞🏻 🎉

I just installed nvim in WSL-2, vscode-neovim extension, and was able to get it to work from a devcontainer with nothing extra in the container.

Having this issue as well

I do wonder what the success of the VSCode Neovim project will have on this project. Also for https://v2.onivim.io/.

I do look forward to finding time to switch to VSCodium (especially in light of https://github.com/iocave/customize-ui/issues/156) and using OpenVSX as an extensions marketplace. Given that OniVim uses the same marketplace and VSCodium has VSCode Neovim, I tend to be rather sceptical of OniVim’s future, especially as it uses a rather exotic framework for its UI (Revery).

Only time will tell.

I tried downgrading the extension to 1.22.0 using VS Code 1.75.0 Darwin arm64 21.6.0 and am still running into the problem. Definitely seems like something changed on the VS Code side.

@ianchanning

I did, but I was looking at the wrong thing, I was focused (no pun intended) on the “Command” column, which has nothing to hint at the job of J in VIM, and didn’t see the “Source” column.

Same here 😦

@edit: Posting “+1” or “Same here” should not be interpreted as unnecessary flooding. It should be, instead, interpreted as a nice way to show to the maintainers that the issue is affecting a large user-base. That’s my goal 😃

We’re all software engineers. Can we put up a PR to fix this rather than piling on with complaints?

I haven’t had time to dig into the code but I found a PR that touched registers from late last year. It shipped in 1.24.3. That’s probably where I’d start looking.

Same issue (intermittently). I noticed it yesterday for the first time. I updated to macOS Ventura 13.1 (from Monterey) on Saturday.

Version: 1.75.0 (Universal) Commit: e2816fe719a4026ffa1ee0189dc89bdfdbafb164 Date: 2023-02-01T15:24:42.903Z (4 days ago) Electron: 19.1.9 Chromium: 102.0.5005.194 Node.js: 16.14.2 V8: 10.2.154.23-electron.0 OS: Darwin x64 22.2.0 Sandboxed: Yes

Same here

版本: 1.75.0 (user setup)
提交: e2816fe719a4026ffa1ee0189dc89bdfdbafb164
日期: 2023-02-01T15:23:45.584Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.22621
沙盒化: No

Downgrading to 1.73.1 fix the bug.

Same for me with VSCode Version 1.74.2 I cannot undo any change done in normal mode without having to use C-z. VscodeVim undo states ‘Already at oldest change’ even without saving inbetween.

I’m a bit confused… iab<Esc>u should undo the entire insertion (“ab”, not just “a”), which is what I’m seeing, at least on VS Code 1.74.2.

If anyone is still experiencing this, please post settings.

Same here.

• VS Code 1.74.0
• Ubuntu 22.04
• vscodevim 1.24.3

this. same here

Same here

I’m having this same problem … I’m using VS Code 1.74.0-insider. I’m using Ubuntu, so I don’t think this is OS related.