Make contributed keybindings consistent
Open
Nobody has claimed this yet.
area/remap
kind/refactor
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
The keybindings we contribute to VSCode are very inconsistent, particularly the "when" expressions. Why do some take into account vim.use<key> and others don't? Why do some exclude/include certain modes? This all makes the remapping system opaque and confusing for users.
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 auditing the contributed VSCode keybindings and comparing their when expressions, especially use of vim.use<key> and mode exclusions. The issue does not name files, tests, or a specific entry point, so first identify where these bindings are defined. Done requires an agreed, consistent remapping behavior that is clear to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100