Lag for key mapping for move up one line
Open
Nobody has claimed this yet.
area/remap
kind/bug
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
When c is mapped to k (move up one line) in Normal mode, pressing c has significant lag.
To Reproduce
settings.jsonincludes the setting:"vim.vimrc.enable": true.vimrcincludes the mapping:noremap c k(ckey moves up one line)- In normal mode, press
c c c. There is lag.
Expected behavior
There should be no lag.
Environment (please complete the following information):
- Extension (VsCodeVim) version:
- VSCode version: Bug introduced in 1.21.0
- OS: Mac 11.3.1
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 lag in VSCodeVim with vim.vimrc.enable set to true and .vimrc containing noremap c k, then press c c c in Normal mode. Trace the key-mapping path involved in handling the remapped c key. Done means repeated presses of c move up one line without significant lag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100