Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screen scrolls with cursor if code is folded #4643

Closed
siddharth-krishna opened this issue Mar 11, 2020 · 2 comments
Closed

Screen scrolls with cursor if code is folded #4643

siddharth-krishna opened this issue Mar 11, 2020 · 2 comments

Comments

@siddharth-krishna
Copy link

Describe the bug
With the Vim extension enabled, if I have a file open where I've folded some block of code (that I can see on screen) and my cursor is below this folded block, then moving my cursor up and down lines also makes the screen move. The screen moves so that the cursor is always in the center. This happens in both insert and visual modes. However, this does not happen if my cursor is above the folded block of code, and it stops when the folded block moves out of view.

This causes the screen to jump around, and is quite distracting.

To Reproduce
Steps to reproduce the behavior:

  1. Open any file with blocks of code that can be folded, and that is long enough. For example, open a new file and copy the following block into it 100 times:
test
  test test
  test test test
  test test

  1. Scroll to the middle of the file, and then fold one of the blocks.
  2. Now place the cursor below the folded block, and try to move the cursor downwards.
  3. See error.

Expected behavior
I expect the cursor to move down, but the screen/view to stay the same. Instead, the screen/view scrolls down, and the cursor remains in the center of the screen.

Environment

  • Extension (VsCodeVim) version: 1.13.0
  • VSCode version: 1.43.0
  • OS: Windows 10
@anhtukhtn
Copy link

anhtukhtn commented Mar 13, 2020

I have this issue too.
Extension (VsCodeVim) version: 1.13.0
VSCode version: 1.42.1 (update to 1.43.0 still got the issue)
OS: MacOS 10.14.6

I have to switch to use simple Vim when waiting it's fixed

@tuledev
Copy link

tuledev commented Mar 17, 2020

Downgrade Vim to 1.12.4 will fix the issue
#4632

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants