unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
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 16:49:59 +0300	[thread overview]
Message-ID: <83a5tsrf94.fsf@gnu.org> (raw)
In-Reply-To: <87r0n498u4.fsf@yahoo.com> (message from Po Lu on Mon, 11 Sep 2023 20:45:55 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: stefankangas@gmail.com,  larsi@gnus.org,  57970@debbugs.gnu.org
> Date: Mon, 11 Sep 2023 20:45:55 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.

It sounds like your comments actually agree with my suggestions ;-)

To clarify, I didn't mean that pixel-scroll-precision-mode _cannot_ be
used with wheels, I just said pixel-scroll-mode is _better_ there
(because it requires no tricky configuration); conversely, for
touchpads, pixel-scroll-precision-mode produces a much better UX OOTB.

This particular discussion is about two modes that have very similar
names.  I think explaining the strengths and weaknesses (even if they
are minor and can be overcome, given enough efforts) goes at least
some way towards resolving user confusion about these two, and
changing the name, even if not 110% accurate, is even better.





  reply	other threads:[~2023-09-11 13:49 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
2023-09-11 13:49               ` Eli Zaretskii [this message]
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=83a5tsrf94.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57970@debbugs.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).