Escape keybind conflict in notebook
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
In notebook mode there is a conflict between the escape keybind when waiting for the second key of vim commands.
For example, typing d<esc> will trigger vscode's own escape function, instead of cancelling the d command. Further, vim mode is stuck waiting for the d command to complete in this case. I usually end up hitting escape to get of this mess.
Hitting escape in insert mode does work properly.
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
Reproduce the conflict in notebook mode with the d<esc> sequence, then trace the pending Vim command handling and VS Code's escape keybinding. Compare the behavior with escape in insert mode; done means escape cancels the pending d command without invoking VS Code's escape action or leaving Vim mode waiting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100