Switching between modes makes commands stop working
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
Although commands are working and everything looks normal right after initialization, as soon as I make the first switching between modes(insert or visual) custom commands involving the leader key(in my case, the space bar) stop working.
To Reproduce
Steps to reproduce the behavior:
- Initialize vscode
- Await the extensions to be loaded
- Switch modes
- Custom commands not working from now.
Expected behavior
Custom commands like e mapped to toggle file explorer should work normally.
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.29.0
- VSCode version: 1.97.2
- OS: Ubuntu 24.04.02
Additional context
I have an almost equal copy of the Ubuntu config in a Windows 11, and there I don't find this behavior.
My escape key is mapped to caps lock and it's working. Don't see relation with problem but think it's worth to mention.
Config files in the attachments.
Great thanks for the attention, any help is welcome.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in VSCodeVim 1.29.0 on Ubuntu 24.04.02 with the attached keyboard.json and settings.json. Check the leader-key mapping before and after switching between insert and visual modes; done means the custom e command continues to work after mode changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100