-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Option to disable Scroll Beyond Last Line #4962
Comments
Wondering if we should offer a simple boolean, like VS Code, or maybe some more fine grained thing, like a float that represents how much over scrolling occurs. |
A bool would suffice for now. This is an absolute need for me as I cannot stand scrolling beyond the last line. |
I would love to see this option as well |
I really need this bool option, because I can roll down. I think there is still content below, which is not in line with my habits in VSC and IDEA. |
Check out the latest release, there is a new option called Edit Oh, this isn't related to this issue. Thought this option would disable this |
A partial workaround with [
{
"context": "Editor",
"bindings": {
// Prevent scrolling "off-screen" at the bottom of the file
"pageup": "editor::MovePageUp",
"pagedown": "editor::MovePageDown",
}
}
] |
Monitoring this as well. Need this option. |
I'd be very interested in reading a reason from people who like the last line of code at the top of their editor instead of the bottom because I can't imagine why anyone might like it (unless this is some kind of accessibility thing for people who can't move their eyeballs vertically?). |
The only utility I've found is when comparing two files side-by-side and you need the last line to be at a certain height in the display... Anyways I'd also like the bool! :D |
Check for existing issues
Describe the feature
VS Code parity. An option to stop the editor from scrolling and showing all the extra empty space when already at the end of file.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
The text was updated successfully, but these errors were encountered: