Sometimes pressing <leader> cancels previous <leader>
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
Weirdly enough, sometimes pressing double causes vim to think nothing has been pressed. (I see the first leader recognized in the status bar, and then it disappears when I press the leader again.)
To Reproduce
Steps to reproduce the behavior:
- s a r a (some easy motion)
- s a r a (again)
The second time, the leaders cancel, and sneak intercepts our keypresses.
Environment (please complete the following information):
- Issue Type:
Bug - Extension Name:
vim - Extension Version:
1.13.1 - OS Version:
Darwin x64 19.0.0 - VSCode version:
1.45.0-insider
{
"messages": [],
"activationTimes": {
"codeLoadingTime": 1055,
"activateCallTime": 2,
"activateResolvedTime": 208,
"activationReason": {
"startup": true,
"extensionId": {
"value": "vscodevim.vim",
"_lower": "vscodevim.vim"
},
"activationEvent": "*"
}
},
"runtimeErrors": []
}
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
No file or test is named in the issue. Start by reproducing the two leader leader s a r a sequences in the VSCode Vim extension and inspect the leader-key handling and interaction with sneak; done means repeated leaders consistently trigger the motion without being cancelled or intercepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100