From: Stefan Kangas <stefankangas@gmail.com>
To: Po Lu <luangruo@yahoo.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51886@debbugs.gnu.org
Subject: bug#51886: 29.0.50; pixel-scroll-mode garbage collects like crazy
Date: Tue, 20 Sep 2022 23:37:53 -0700 [thread overview]
Message-ID: <CADwFkm=8Dm4Y3AfSzQVKiFA8SVtuWh2AU4wGrpGRYLSa9px6Dw@mail.gmail.com> (raw)
In-Reply-To: <87y1udiily.fsf@yahoo.com>
Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> pixel-scroll-mode is still buggy and generates an incredible amount of
> garbage. However, pixel-scroll-precision-mode was eventually written to
> use its own code, without touching the rest of the code in
> pixel-scroll.el, so this bug report is not as relevant as it used to be.
Is `pixel-scroll-precision-mode' supposed to be a drop-in replacement
for `pixel-scroll-mode'? If yes, how close is it?
> I'm curious as to whether or not there are people still using the old
> pixel-scroll-mode, especially since pixel-scroll-precision-mode should
> now work "out of the box" with wheel mice on X.
With `pixel-scroll-mode', I can see that when I scroll slowly, scrolling
behaves more like it would in Firefox (i.e., smooth rather than not
choppy).
With `pixel-scroll-precision-mode', I'm not sure I can spot any
difference with or without it enabled, when scrolling with the mouse
wheel.
I just found `pixel-scroll-precision-interpolate-page', which makes it
more attractive for me to use. Is there a way to make it scroll faster
though? If not, could we add such an option?
BTW, why isn't there a pixel-scroll defgroup under the scroll group
instead? I tried `M-x customize-group RET pixel TAB' but couldn't find
anything relevant.
next prev parent reply other threads:[~2022-09-21 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ee7gwop0.fsf.ref@yahoo.com>
2021-11-16 7:21 ` bug#51886: 29.0.50; pixel-scroll-mode garbage collects like crazy Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 13:05 ` Eli Zaretskii
2021-11-16 13:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 13:37 ` Eli Zaretskii
2021-11-16 13:28 ` Robert Pluim
2021-11-16 13:38 ` Eli Zaretskii
2021-11-16 13:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 14:35 ` bug#51886: 29.0.50; pixel-scroll-mode garbage collects like crazy, " Robert Pluim
2022-09-20 15:16 ` Lars Ingebrigtsen
2022-09-21 2:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-21 6:37 ` Stefan Kangas [this message]
2022-09-21 7:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-21 8:55 ` Stefan Kangas
2022-09-21 10:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 10:59 ` Stefan Kangas
2024-01-10 11:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADwFkm=8Dm4Y3AfSzQVKiFA8SVtuWh2AU4wGrpGRYLSa9px6Dw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=51886@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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).