From: Eli Zaretskii <eliz@gnu.org>
To: "Herman Géza" <geza.herman@gmail.com>
Cc: 66216@debbugs.gnu.org
Subject: bug#66216: 28.2; scroll-up-line doesn't work if there is a before-string overlay with newline
Date: Fri, 29 Sep 2023 18:28:12 +0300 [thread overview]
Message-ID: <834jjdyp6b.fsf@gnu.org> (raw)
In-Reply-To: <99a86a00-20d8-446f-336a-1f405e07d59f@gmail.com> (message from Herman, Géza on Fri, 29 Sep 2023 13:53:04 +0200)
> Date: Fri, 29 Sep 2023 13:53:04 +0200
> Cc: 66216@debbugs.gnu.org
> From: Herman, Géza <geza.herman@gmail.com>
>
> I have scroll-up/down-line mapped to a key. I'd like to see that if I
> press and hold these keys, Emacs can scroll continuously. It doesn't
> matter too much if at some position, it jumps 2 (or more) visible lines.
> Using prefix arguments is not a good solution for this case, because if
> I have a buffer with a lot of such overlays (like magit's blame buffer),
> it's very inconvenient that emacs stops very frequently, and then I have
> to nag it with a prefix argument to "please scroll further". But of
> course I can try to write some elisp function to work around this
> limitation.
I explained why catering only to this preference will bring us other
problems.
One solution is for you to write a simple function that scrolls by
more than 1 line if the basic scroll didn't change window-start
position.
And if this is a problem with Magit, then I would suggest that Magit
has its own scrolling function to overcome the problems. I tried to
explain many times that using overlays and display properties in Magit
buffers was a bad idea, and the Magit developer even agreed with me at
some point.
> As scroll-down-line jumps over overlays, so it already scrolls 2 visible
> lines in the mentioned case, it would make sense that scroll-up-line
> behaves the same as well. The current behavior is not consistent. I'd
> expect that if scroll-down-line moves window start somewhere, then
> scroll-up-line will undo this. But in this case scroll-down-line will
> move 2 lines, then scroll-up-line doesn't do anything.
The situation with scroll-down and scroll-up is not symmetric.
next prev parent reply other threads:[~2023-09-29 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 18:30 bug#66216: 28.2; scroll-up-line doesn't work if there is a before-string overlay with newline Herman, Géza
2023-09-29 11:28 ` Eli Zaretskii
2023-09-29 11:53 ` Herman, Géza
2023-09-29 15:28 ` Eli Zaretskii [this message]
2023-09-30 17:09 ` Herman, Géza
2023-09-30 17:17 ` Eli Zaretskii
2023-09-30 17:29 ` Herman, Géza
2023-09-30 17:37 ` Eli Zaretskii
2023-09-30 19:15 ` Herman, Géza
2023-10-01 8:51 ` Eli Zaretskii
2023-10-01 12:10 ` Herman, Géza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834jjdyp6b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66216@debbugs.gnu.org \
--cc=geza.herman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).