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

editor.cursorSurroundingLines cannot reduce the default #222178

Closed
aavogt opened this issue Jul 19, 2024 · 1 comment
Closed

editor.cursorSurroundingLines cannot reduce the default #222178

aavogt opened this issue Jul 19, 2024 · 1 comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@aavogt
Copy link

aavogt commented Jul 19, 2024

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: Version: 1.91.1
    Commit: f1e16e1
    Date: 2024-07-09T22:08:12.169Z
    Electron: 29.4.0
    ElectronBuildId: 9728852
    Chromium: 122.0.6261.156
    Node.js: 20.9.0
    V8: 12.2.281.27-electron.0
    OS: Linux x64 6.5.0-41-generic
  • OS Version: Ubuntu 22.04.4 LTS

Steps to Reproduce:

  1. open a long file
  2. go to the bottom of the file (C-end)
  3. put the cursor at the first visible line with the mouse
  4. press the up arrow key
  5. let the number of lines visible above the cursor be U

U = max(5, editor.cursorSurroundingLines). Going down, the number of lines below is D= max(1, editor.cursorSurroundingLines).

I expected editor.cursorSurroundingLines=0 to make the U D gaps 0. I don't think the default behavior should change -- I want to be able to set the scrolling to be like vim's default scrolloff=0.

@rebornix rebornix added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 19, 2024
@aavogt
Copy link
Author

aavogt commented Dec 19, 2024

#204193

@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Feb 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants