VSCodeVim / VSCodeVim/Vim

Leader mappings stop resolving after using VS Code debugger until window reload

Open
#9,997 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

Description

After using the VS Code debugger, VSCodeVim stops resolving custom leader mappings until the window is reloaded.

Important detail: Vim itself is still active and still receives keys.

  • Pressing <space> is still recognized as leader
  • The Vim log shows both keys being handled
  • Built-in Vim motions like w, b, and text objects such as ci( still work
  • Native VS Code shortcuts like Ctrl+Shift+P still work
  • Only custom leader mappings stop working
  • Developer: Reload Window restores the mappings immediately
Environment
  • VS Code version: 1.117.0
  • VSCodeVim version: 1.32.4
  • OS: Windows
Minimal configuration
{
  "vim.leader": "<Space>",
  "vim.useCtrlKeys": true,
  "vim.normalModeKeyBindings": [
    {
      "before": ["leader", "f"],
      "commands": ["workbench.action.quickOpen"]
    }
  ],
  "vim.normalModeKeyBindingsNonRecursive": [
    {
      "before": ["leader", "<Space>"],
      "commands": ["workbench.action.showCommands"]
    }
  ]
}
Steps to reproduce
  1. Configure:
    • <space> f -> workbench.action.quickOpen
    • <space> <space> -> workbench.action.showCommands
  2. Verify both mappings work.
  3. Start and use a debug session.
  4. Return to the editor.
  5. Try the mappings again.

Result: mappings no longer execute until Developer: Reload Window.

This issue could be related: https://github.com/VSCodeVim/Vim/issues/7595

Vim debug log
2026-04-29 18:37:16.169 [debug] Handling key: <space>
2026-04-29 18:37:16.271 [debug] Handling key: f
2026-04-29 18:37:18.124 [debug] Status bar: -- NORMAL --
...
2026-04-29 18:37:37.095 [debug] Handling key: <space>
2026-04-29 18:37:37.535 [debug] Handling key: f

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the provided VS Code settings, first confirming both leader mappings work before and fail after a debug session. Trace the key-handling path using the Vim debug log and compare behavior before and after debugging; done means both mappings execute again without requiring Developer: Reload Window.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.