From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: luangruo@yahoo.com, rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: master e37eb7f: Add support for pixel wheel deltas on NS
Date: Fri, 26 Nov 2021 21:45:43 +0200 [thread overview]
Message-ID: <83sfvi1z14.fsf@gnu.org> (raw)
In-Reply-To: <YaE3+96bT/tjZLow@idiocy.org> (message from Alan Third on Fri, 26 Nov 2021 19:39:39 +0000)
> Date: Fri, 26 Nov 2021 19:39:39 +0000
> From: Alan Third <alan@idiocy.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, rpluim@gmail.com, emacs-devel@gnu.org
>
> On Fri, Nov 26, 2021 at 08:37:08PM +0800, Po Lu wrote:
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > It's simple: we could provide a variable to scale the pixels
> > > calculated by the *term code.
> >
> > Alternatively, how about putting such an option in the code that makes
> > use of such events, something like `pixel-scroll-precision-scale'.
>
> Why not move the delta to pixel conversion to lisp?
Move it how? Having each wheel event call into Lisp is not something
I'd like to do.
What kind of conversion do we need that is not a simple multiplication
by a user-customizable fixed value? If this is all we need, the
conversion could be performed by the calling application.
next prev parent reply other threads:[~2021-11-26 19:45 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211125030922.2353.1129@vcs0.savannah.gnu.org>
[not found] ` <20211125030924.7258E2094B@vcs0.savannah.gnu.org>
2021-11-25 10:26 ` master e37eb7f: Add support for pixel wheel deltas on NS Robert Pluim
2021-11-25 10:34 ` Po Lu
2021-11-25 10:47 ` Robert Pluim
2021-11-25 11:02 ` Eli Zaretskii
2021-11-26 0:39 ` Po Lu
2021-11-26 6:35 ` Eli Zaretskii
2021-11-26 7:00 ` Po Lu
2021-11-26 8:17 ` Eli Zaretskii
2021-11-26 9:37 ` Po Lu
2021-11-26 11:32 ` Eli Zaretskii
2021-11-26 11:44 ` Po Lu
2021-11-26 16:55 ` Eli Zaretskii
2021-11-27 0:02 ` Po Lu
2021-11-27 6:09 ` Eli Zaretskii
2021-11-27 6:41 ` Po Lu
2021-11-27 7:05 ` Eli Zaretskii
2021-11-27 7:14 ` Po Lu
2021-11-27 10:47 ` Eli Zaretskii
2021-11-27 10:54 ` Po Lu
2021-11-27 11:03 ` Eli Zaretskii
2021-11-27 11:05 ` Po Lu
2021-11-27 11:13 ` Po Lu
2021-11-27 11:32 ` Eli Zaretskii
2021-11-27 11:34 ` Po Lu
2021-11-27 11:40 ` Eli Zaretskii
2021-11-27 11:44 ` Po Lu
2021-11-27 12:02 ` Eli Zaretskii
2021-11-27 12:11 ` Po Lu
2021-11-27 12:36 ` Eli Zaretskii
2021-11-27 12:48 ` Po Lu
2021-11-26 11:48 ` Eli Zaretskii
2021-11-26 12:05 ` Po Lu
2021-11-26 12:23 ` Eli Zaretskii
2021-11-26 12:37 ` Po Lu
2021-11-26 19:39 ` Alan Third
2021-11-26 19:45 ` Eli Zaretskii [this message]
2021-11-26 19:54 ` Alan Third
2021-11-28 2:54 ` Po Lu
2021-11-28 7:53 ` Eli Zaretskii
2021-11-28 7:58 ` Po Lu
2021-11-28 8:28 ` Eli Zaretskii
2021-11-29 7:39 ` Po Lu
2021-11-29 12:50 ` Eli Zaretskii
2021-11-29 13:19 ` Po Lu
2021-11-25 11:00 ` Eli Zaretskii
2021-11-25 18:46 ` Stefan Monnier
2021-11-25 18:58 ` Eli Zaretskii
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=83sfvi1z14.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=rpluim@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).