unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jared Finder via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 68050@debbugs.gnu.org, 68050-done@debbugs.gnu.org
Subject: bug#68050: 29.1; Pixel scroll doesn't work on platforms that do not expose device-class.
Date: Wed, 27 Dec 2023 17:13:33 -0800	[thread overview]
Message-ID: <d8ec9b6e8b86139ca8d99367a6e12a20@finder.org> (raw)
In-Reply-To: <8734vocsg6.fsf@yahoo.com>

On 2023-12-26 18:03, Po Lu wrote:
> Jared Finder <jared@finder.org> writes:
> 
>> I'm a bit confused by the "this isn't necessary" response.  What
>> should I be doing on Mac or on Windows, where Emacs doesn't
>> distinguish between touchpads and mice currently?  Is there a fix in
>> the works for these OSes?
> 
> As I said, set pixel-scroll-precision-large-scroll-height to a value
> such that events sent by mice are classified as such and interpolated,
> or 0, which will direct Emacs to apply interpolation to all scroll
> events.

Thank you so much! This works as a replacement of my original patch.

   -- MJF





      reply	other threads:[~2023-12-28  1:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 21:01 bug#68050: 29.1; Pixel scroll doesn't work on platforms that do not expose device-class Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-27  1:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-27  1:32   ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-27  2:03     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-28  1:13       ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=d8ec9b6e8b86139ca8d99367a6e12a20@finder.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=68050-done@debbugs.gnu.org \
    --cc=68050@debbugs.gnu.org \
    --cc=jared@finder.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).