From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61307@debbugs.gnu.org
Subject: bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions?
Date: Thu, 16 Feb 2023 05:57:18 +0100 [thread overview]
Message-ID: <877cwi1a35.fsf@web.de> (raw)
In-Reply-To: <83y1ozawtu.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 15 Feb 2023 15:21:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> > > 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?
> 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.)
[ I'm sorry, I totally misunderstood your question as rhetorical, for me
to think and understand ]
I'm using a normal wheel mouse. I have nevertheless enabled
`pixel-scroll-precision-mode' for two reasons: I want to have the
animated "smooth scrolling" like known from browsers, which looks nicer
and seems to be better for the eyes/ the brain. And I want to get a
better scrolling experience for images (pdf, and such things).
And the answer to your question is: I get a scroll amount of
approximately 7 lines per <wheel-up> or <wheel-down> event. I
configured pixel-scroll-precision-interpolation-factor to 1.5, the
original value of 2.0 was a bit too large in my experience.
> > 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.
Is receiving <wheel-up> and <wheel-down> events a sufficient hint that
the user is scrolling using a "normal" wheel mouse?
Michael.
next prev parent reply other threads:[~2023-02-16 4:57 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
2023-02-16 4:57 ` Michael Heerdegen [this message]
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
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=877cwi1a35.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=61307@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).