Currently in vims "more prompt" using ctrl + f/b is not possible.
Move forward or backward one screen in a more prompt with ctrl + f/b is possible.
Inside vim you move forward/backwards one screen with ctrl + f/b.
Not being able to do this in a more prompt is inconsistent.
I use ctrl + f/b in a lot of tools (bat, less, zathura) and always
trip over this not working in vims "more prompt".
https://github.com/vim/vim/pull/18545
(2 files)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
thanks. Can you please create a test for this?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@bfoersterling pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
thanks. Can you please create a test for this?
Yes, sorry, I have added the tests to Test_message_more().
I have noticed one edge case though.
When being at the bottom of the more prompt CTRL-B/CTRL-F will quit the more prompt.
Just typing f or b will not do this.
I have not figured out why this happens.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@bfoersterling pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@bfoersterling pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@bfoersterling pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
So the issue is fixed, the keys needed to be added to wait_return() as well.
Now I only need to get the code coverage.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@bfoersterling pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@bfoersterling pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
Thanks. I think it should be fine, code coverage display is a bit flaky anyhow, so don't worry too much
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()