unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 57970@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#57970: 29.0.50; Create new defgroup for pixel-scroll.el
Date: Mon, 11 Sep 2023 20:45:55 +0800	[thread overview]
Message-ID: <87r0n498u4.fsf@yahoo.com> (raw)
In-Reply-To: <83il8griju.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Sep 2023 15:38:45 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 57970@debbugs.gnu.org
>> Date: Mon, 11 Sep 2023 16:37:10 +0800
>> From:  Po Lu via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> Stefan Kangas <stefankangas@gmail.com> writes:
>> 
>> > I'm still not sure what is the relationship with pixel-scroll-mode.  Eli
>> > does, I think.  So it might be best to send any suggested changes to the
>> > bug tracker.
>> 
>> For what it's worth, the only advantage the old pixel-scroll-mode has
>> over p-s-p-m is that it functions with regular wheel mice by default.
>> 
>> pixel-scroll-precision-mode is also capable of supporting wheel mice,
>> but detecting them and enabling the requisite options is tricky and
>> subject to numerous edge cases, so those options remain off by default.
>
> So maybe we should document that one is better for wheels, the other
> for touchpads?  And maybe even (gasp!) rename
> pixel-scroll-precision-mode to something like touchpad-scroll-mode?

pixel-scroll-mode isn't better for wheel mice as long as you actually
tell p-s-p-m that you use one, so that assessment isn't really correct.

pixel-scroll-mode's principal failings are that it bails out when a
wheel event arrives while scrolling is taking place, it always scrolls
by a set number of lines, and it is slow.  p-s-p-m experiences none of
these problems.





  reply	other threads:[~2023-09-11 12:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21  8:02 bug#57970: 29.0.50; Create new defgroup for pixel-scroll.el Stefan Kangas
2022-09-21 11:47 ` Lars Ingebrigtsen
2022-09-21 13:51   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-21 14:03     ` Lars Ingebrigtsen
2023-09-11  0:21       ` Stefan Kangas
2023-09-11  8:37         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 12:38           ` Eli Zaretskii
2023-09-11 12:45             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-11 13:49               ` Eli Zaretskii
2023-09-11 14:46                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 15:52                   ` Eli Zaretskii
2023-09-11  0:17   ` Stefan Kangas

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=87r0n498u4.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=57970@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=stefankangas@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).