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 22:46:03 +0800 [thread overview]
Message-ID: <s0dbke8g444.fsf@yahoo.com> (raw)
In-Reply-To: <83a5tsrf94.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Sep 2023 16:49:59 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> 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.
That is correct, but not from an objective standpoint, only from the POV
of what is better "out of the box". p-s-p-m is worse off OOTB, because
it takes no effect at all without some configuration.
> 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.
Users customarily search for terms in the vein of "pixel scroll", which
that must still be taken into account: whatever name we select for the
mode should incorporate the word "pixel".
One more data point: within the stream of feature requests that
constitued the impetus for my decision to implement this feature, not a
single request mentioned the word "touchpad", whereas "pixel" and
"precise" abounded. At least in my recollection.
next prev parent reply other threads:[~2023-09-11 14:46 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
2023-09-11 14:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s0dbke8g444.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 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.