Key mappings in .vimrc not overriding in the order they appear in the configuration
Open
Nobody has claimed this yet.
area/remap
area/vimrc
kind/bug
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
To Reproduce
Write in .vimrc:
nmap ss :echo "first"<CR>
nmap ss :echo "second"<CR>
Expected behavior
When ss triggerred, it should print second.
But first is shown.
Screenshots
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.32.1
- VSCode version: 1.105.1
- OS: win11 26200.7171
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 two consecutive nmap definitions in .vimrc with VSCodeVim 1.32.1, VS Code 1.105.1, and the reported Windows environment. Trace how the extension loads and resolves these mappings; done means triggering ss prints "second" rather than "first".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vim, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100