From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 68698@debbugs.gnu.org
Subject: bug#68698: 30.0.50; Making xt-mouse emit `wheel-up/down`
Date: Thu, 25 Jan 2024 10:25:53 +0800 [thread overview]
Message-ID: <87sf2mp2ry.fsf@yahoo.com> (raw)
In-Reply-To: <jwvjznyxyl7.fsf@iro.umontreal.ca> (Stefan Monnier's message of "Wed, 24 Jan 2024 15:31:32 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The second step would be to do something similar for the non-XInput2 X11
> build: make it generate `wheel-up/down` events according to
> `mouse-wheel-down/up-event` settings. Then packages like
> `completion-preview` and `mwheel` won't need to pay attention to the
> (confusingly named) `mouse-wheel-down/up-event` vars any more.
No!
Button4, 5, 6 and 7 are only mouse wheels in one particular group of X
servers. It is impossible to detect whether they are mouse wheels
without the input extension (and this is why XI display connections
produce wheel events), so such an escape hatch as mouse-wheel-*-event
_must_ be provided for X servers where the general assumption that they
are mouse wheels does not hold true.
next prev parent reply other threads:[~2024-01-25 2:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 20:31 bug#68698: 30.0.50; Making xt-mouse emit `wheel-up/down` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-25 2:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-01-25 13:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-25 14:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-25 15:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-26 1:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-26 2:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-25 7:30 ` Eli Zaretskii
2024-01-26 1:41 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-26 2:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-26 5:02 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-26 7:56 ` Eli Zaretskii
2024-01-26 13:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28 23:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87sf2mp2ry.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=68698@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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).