VSCodeVim / VSCodeVim/Vim

Cursor can't move after moving in git diff editor

Open
#8,953 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug

Cursor can't move after moving in git diff editor

To Reproduce
Steps to reproduce the behavior:

  1. change a file and open the diff editor
  2. hidden unchanged regions
  3. make sure the first line is not 1
  4. type gg to move to the first line, and type k to move up
  5. then the cursor can't move again with any motion, even if in other files

Expected behavior
it should work

Screenshots
If applicable, add screenshots to help explain your problem.
If remapping-related, please attach log output: https://github.com/VSCodeVim/Vim#debugging-remappings.
Screenshot 2024-03-21 at 18 06 27

Environment (please complete the following information):

  • Extension (VsCodeVim) version:
  • VSCode version:
  • OS:

Additional context
Add any other context about the problem here.

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

Reproduce the issue in the VSCodeVim extension using a Git diff editor with unchanged regions hidden, ensuring the first line is not 1. Follow the gg then k motion sequence and verify whether subsequent motions remain blocked, including in another file; done means cursor movement works normally after this sequence.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.