From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 61307@debbugs.gnu.org
Subject: bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions?
Date: Wed, 15 Feb 2023 15:21:17 +0200 [thread overview]
Message-ID: <83y1ozawtu.fsf@gnu.org> (raw)
In-Reply-To: <87sff7374b.fsf@web.de> (message from Michael Heerdegen on Wed, 15 Feb 2023 05:06:12 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 61307@debbugs.gnu.org
> Date: Wed, 15 Feb 2023 05:06:12 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > I don't see the hook called for each pixel. What do you mean?
> >
> > Each time you do the smallest possible scroll, by how many pixels, or
> > by what fraction of the screen-line's height does Emacs scroll the
> > window? IOW, by how many pixels is the display scrolled for each call
> > to window-scroll-functions?
> >
> > Precision pixel-scrolling supports many different devices (mice and
> > touch-pads), which can scroll at very different resolutions. The
> > possibility that window-scroll-functions be called too frequently
> > depends on what exactly do your device and your Emacs build support in
> > this scenario, and I don't yet have a clear idea about that, since you
> > didn't tell.
>
> I feel a bit lost. What should I tell? I have no idea what I could
> know about this that you don't already know.
I hoped you will answer the specific questions I asked, quoted above.
But since you don't have a device to actually observe
pixel-scroll-precision-mode on your system, something I didn't know
until now, I guess you cannot answer them? (I also don't have access
to a suitable system, otherwise I wouldn't have bothered you with the
questions.)
> But I understand that what I see when scrolling with a normal wheel
> mouse is only one case we need to handle.
Right. Though on such a system, we should probably call
window-scroll-functions every scroll.
> AFAIU, scrolling by
> dragging the vertical scroll bar is not handled by precision scrolling.
Correct.
> So we speak about touch events (although
> `pixel-scroll-precision-mode-map' only binds <touch-end>, but that event
> may also be generated very often) and mice with a more or less
> continuous scroll wheel (or ball) and such things.
Yes, capable mice (which also require a capable system to support
them), and touch pads.
> Or would you suggest to call the window-scroll functions just after a
> certain time limit?
I don't think a timer would be appropriate here.
> A pixel-delta limit would probably not be
> sufficient, since we want to call the functions also for small scroll
> amounts if they are not directly followed by another scroll (I guess).
Not necessarily. To see a similar situation, disable
image-auto-resize mode, visit a large image, and scroll with C-n or
C-p: you won't see window-scroll-functions called at all. That's
basically what pixel-scroll-precision-mode works: it uses the window's
vscroll, like we do with tall images.
next prev parent reply other threads:[~2023-02-15 13:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 1:49 bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions? Michael Heerdegen
2023-02-06 12:15 ` Eli Zaretskii
2023-02-06 21:30 ` Michael Heerdegen
2023-02-12 12:15 ` Eli Zaretskii
2023-02-13 2:20 ` Michael Heerdegen
2023-02-13 3:31 ` Eli Zaretskii
2023-02-13 3:44 ` Michael Heerdegen
2023-02-13 12:56 ` Eli Zaretskii
2023-02-14 1:30 ` Michael Heerdegen
2023-02-14 13:06 ` Eli Zaretskii
2023-02-15 4:06 ` Michael Heerdegen
2023-02-15 13:21 ` Eli Zaretskii [this message]
2023-02-16 4:57 ` Michael Heerdegen
2023-02-16 8:22 ` Eli Zaretskii
2023-02-16 8:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-16 8:54 ` Michael Heerdegen
2023-02-19 5:50 ` Michael Heerdegen
2023-02-19 6:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 7:36 ` Michael Heerdegen
2023-02-19 8:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-06 14:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-06 15:25 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1ozawtu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61307@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.