Implement `:map` to allow the user to visualize the existing remaps
Open
Nobody has claimed this yet.
area/remap
kind/feature
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Implement :map and its multiple variants like :nm[ap], :im[ap], :vm[ap], :no[remap] :unm[ap], :nun[map], etc to check what keys are mapped to what.
Also implement a way of creating <buffer> only remaps using these commands. This requires having 'local' remaps per editor (document).
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 files, tests, or entry points are named. Start by locating the remap and keybinding handling in the TypeScript extension, then trace how editor-local state is represented. Done means the listed :map variants can inspect and create remaps, including buffer-local remaps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100