Closed soifou closed 1 month ago
Thanks for the suggestions! No idea why I didnt implement scrolloff yet since I use it in my vim as well. Anyway, it is now in if you build from master: https://mierak.github.io/rmpc/configuration/#scrolloff
The non-wrapping Up/Down will happen soon too.
Wow... that was fast! I'm using it right now and it works nicely, thanks!
Glad it works fine! Anyway, the wrapping is now gone by default and can be configured back with https://mierak.github.io/rmpc/configuration/#wrap_navigation.
Mini feedback, I noticed the scrollback indicator is not in phase anymore. When the first item is selected, the scrollback is not at the very top but slightly below, and on a (very) long list, it disappears on the last items.
It looks like a regression.
Hmm, I cant reproduce the issue. Can you give me more info? Config and theme, terminal and maybe a screenshot would help.
Sure, I tracked down the issue and the culprit seems to be the symbols used for the scrollbar:
scrollbar: (
symbols: ["", "┃", "", ""],
// ...
),
If I change with the default, there is no problem. I did not notice this in previous version.
Thanks! I see the problem now. Though for me its been there since forever, at least since 0.4.0. I'll look into it!
Fix is merged to master https://github.com/mierak/rmpc/pull/100
Confirmed 👍 thanks again :)
When you are on the last item on any list, pressing
Down
go to the first item and conversely, pressingUp
on the first item go to last item.I think allowing to 'cycle' should be an opt-in behaviour. By default, as in ncmpcpp, a sane way would be to do... nothing. If I need to go to first/last,
Top/Bottom
actions can already do that.In the same registry, a "nice to have" would be to implement a
scrolloff
option like in vim (minimal number of screen lines to keep above and below the current selected item) so we could better predict what will go next/prev.