From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master e37eb7f: Add support for pixel wheel deltas on NS
Date: Sat, 27 Nov 2021 19:05:50 +0800 [thread overview]
Message-ID: <87k0gtc0z5.fsf@yahoo.com> (raw)
In-Reply-To: <83tufxzwq9.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Nov 2021 13:03:42 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: emacs-devel@gnu.org
>> Date: Sat, 27 Nov 2021 18:54:42 +0800
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > The event may have additional arguments after
>> > @var{position}. The third argument after @var{position}, if present,
>> > is a pair of the form @w{@code{(@var{x} . @var{y})}}, where @var{x}
>> > and @var{y} are the number of pixels to scroll by in each axis.
>>
>> > It mentions the 3rd argument (starting from 1, I presume, given the
>> > format of the event shown in @item). But the code in pixel-scroll.el
>> > does:
>>
>> It says "the third argument after @var{position}", which is the fifth
>> element (1-based) in the lispy event, as position is the second element
>> (again, one-based) of the event.
>>
>> But I agree that the wording is confusing and can probably be improved
>> to just mention that the fifth element contains the pixel information.
> So what are the two arguments between POSITION and (X . Y), the 3rd
> and the 4th elements in the Lispy event? They should be documented in
> the general form of the event.
I have no idea what they are, and as such couldn't document them. (They
are not related to the pixel scrolling support.)
But I will try to find out.
Thanks.
next prev parent reply other threads:[~2021-11-27 11:05 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0gtc0z5.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.