I was going to ask if you would consider adding g/G to the |more-
prompt| in message.c:msg_moremsg() like so:
2922c2922
< _(" SPACE/d/j: screen/page/line down, b/u/k: up, first/
last: g/G, q: quit "),
---
> _(" SPACE/d/j: screen/page/line down, b/u/k: up, q: quit "),
....which I am still asking. ;-) My reasoning is that the
enumeration of all these other inputs in this more message implies
that it is an exhaustive list, and (ignoring backspace which is
already redundant) this would make it so. This is a particularly
useful tidbit of knowledge to have when you've set verbose very high
and have tons of autocmds firing off.
Then, while playing with g and G, I noticed an issue:
vim -u NONE --cmd 'set nocompatible | echo "hi\nthere"'
Now if I hit gGgGgGgGgG..., a blank line is added below the last line
each time I hit G, so the paged output "walks" upwards. This is a
minimal test case, but you'll see this happening everywhere there is
paged output in vim that is shorter than the height of your window.
For example, :let, :!date, :cscope, etc.
Ahoy,
CS
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
