Be smarter with `editor.action.wordHighlight.trigger` to prevent flashing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Each call to ModeHandler.updateView calls editor.action.wordHighlight.trigger, causing VS Code to re-evaluate the word highlight. This causes it to disappear and reappear with every motion as you move across a word (with l, for instance). Without VSCodeVim, this doesn't happen. We should be able to remember the last word we were on, and only trigger an update when we're no longer on that word.
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 at ModeHandler.updateView and trace its calls to editor.action.wordHighlight.trigger. Determine how the current word can be remembered across motions, then verify that highlighting is refreshed only after moving to a different word and no longer flashes during movement.
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
- 48/100