You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, with the default keybindings in micro, pressing PageUp or PageDown moves the cursor one page up or down, and scrolls the view by the minimum amount necessary.
I would prefer the PageUp / PageDown behaviour from nano. It always scrolls the view and the cursor by the same amount (buffer line count permitting), which helps a lot in keeping track of where my cursor is, and which part of the file I'm looking at.
In other words, in nano, when my cursor is in the middle of the screen, and I press PageUp or PageDown, and scrolling by a full page is possible, then the view will be scrolled by a full page, and my cursor will still be in the middle of the screen. It means I don't have to keep scanning the whole screen to reorient myself as I page up and down, and it makes it easier (at least IMO) to reposition the cursor once I'm done scrolling.
I can imagine that the nano way might not be the most intuitive for everyone, so I'd like to propose for this to be a config option.
There is also another issue that ties into this. Nano preserves 2 lines of overlap between pages, which is helpful when reading or visually scanning the buffer across pages (the last 2 lines of one page are the first 2 lines of the next page). Micro not only doesn't do that currently, it actually skips one line entirely. I think this could be addressed by making sure micro preserves an overlap equal to scrollmargin.
Specifications
Version: 2.0.6
Commit hash: 60846f5
Compiled on July 03, 2020
OS: Manjaro
Terminal: Konsole
The text was updated successfully, but these errors were encountered:
As a fellow nano-ite who finds micro attractive, I was also strugging with the pageup/pagedown behavior. I do find the CursorPageUp and CursorPageDownactions /closer/ to how I hope for it to work and have settled on that.
I experimented with using "ScrollDown""ScrollUp" and tinkering with scrollspeed to compensate prior to that and it didn't quite fit the need.
Description of the problem or steps to reproduce
Currently, with the default keybindings in micro, pressing PageUp or PageDown moves the cursor one page up or down, and scrolls the view by the minimum amount necessary.
I would prefer the PageUp / PageDown behaviour from nano. It always scrolls the view and the cursor by the same amount (buffer line count permitting), which helps a lot in keeping track of where my cursor is, and which part of the file I'm looking at.
In other words, in nano, when my cursor is in the middle of the screen, and I press PageUp or PageDown, and scrolling by a full page is possible, then the view will be scrolled by a full page, and my cursor will still be in the middle of the screen. It means I don't have to keep scanning the whole screen to reorient myself as I page up and down, and it makes it easier (at least IMO) to reposition the cursor once I'm done scrolling.
I can imagine that the nano way might not be the most intuitive for everyone, so I'd like to propose for this to be a config option.
There is also another issue that ties into this. Nano preserves 2 lines of overlap between pages, which is helpful when reading or visually scanning the buffer across pages (the last 2 lines of one page are the first 2 lines of the next page). Micro not only doesn't do that currently, it actually skips one line entirely. I think this could be addressed by making sure micro preserves an overlap equal to
scrollmargin
.Specifications
Version: 2.0.6
Commit hash: 60846f5
Compiled on July 03, 2020
OS: Manjaro
Terminal: Konsole
The text was updated successfully, but these errors were encountered: