-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Optimize scrolling UI #54
Comments
I forgot to make the limit dynamic. it's an easy fix.
This depends on fdehau/tui-rs#328 |
Ah got it... Let me see how to implement this (without sacrificing performance). |
Reopening this as the navigation isn't vim-like yet. |
I think we have an easy and "good enough" scrolling system. Some plugins have adapted to this system to calculate the display area of the content in a layout. Making a stateful scrolling system will contribute to the complexity not only for xplr, but those plugins as well. So, being not interested in doing so, closing this issue. |
I'd really like to see this introduced. I believe XPLR is nearing perfection except for the current scrolling behavior which is so annoying and feels weirdly outstanding among all the CLI tools I regularly use. |
I expect
xplr
to show as much files as it could possibly fit, but in fact there is a lot of empty unused space:If I begin to scroll down, it's not using more space:
If I resize terminal such that there is less vertical space, xplr even adjusts on the fly - but if I resize back, at some point it just stops using extra space, resulting in the pictures above.
It would be nice to always use all the available space 🙂
Furthermore, once you scroll down (like on the second picture above - so I'm on 946), and then I begin to scroll up again, I expect the cursor to go up but I expect
946
to still be in the view, i.e. view should not be scrolled at this point - like try scrolling up and down in vim in a long document, cursor goes up but screen scrolling should only begin when cursor reaches the top of the screen. Does this make sense? And what do you think in general? 🙂The text was updated successfully, but these errors were encountered: