VSCodeVim / VSCodeVim/Vim

Jumping to Previous Position After Pressing a Key

Open
#9,195 12 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

Describe the bug
When searching for a symbol in VS Code, after finding the symbol and navigating to it, pressing any key on the keyboard causes the cursor to jump back to its previous position.

To Reproduce
Steps to reproduce the behavior:

  1. Toggle the search symbol in VS code ( Ctrl + Shift + o ) or (Ctrl + p ) and then type "@"
  2. start searching for a symbol that you want to go to
  3. click the symbol or press enter
  4. start pressing any key

Expected behavior
After navigating to the symbol I want to go to, the cursor should not jump back to its previous position after pressing any key.

Environment

  • Extension (VsCodeVim) version: v1.27.3
  • VSCode version: 1.92.1
  • OS: Windows 10 ( Windows_NT x64 10.0.19045)

Additional context
This issue is not limited to searching for a symbol. If I also search for a word by pressing (Ctrl + F) and then navigate to that word, pressing any key causes the cursor to jump back to its previous position. This bug does not always occur, sometimes it doesn’t happen, and I’m still unsure what triggers it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reproducing the jump after symbol and word searches on the listed VS Code and Windows versions, then trace how navigation state is restored when the next key is handled. Done means the cursor remains at the selected location across both search flows and the intermittent trigger is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.