unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ami Fischman <ami@fischman.org>
Cc: 66765@debbugs.gnu.org
Subject: bug#66765: closed (Re: bug#66765: 30.0.50; Building emacs with xinput2 breaks receiving XSendEvent events)
Date: Sun, 29 Oct 2023 08:43:07 +0800	[thread overview]
Message-ID: <s0dh6ma9s2s.fsf@yahoo.com> (raw)
In-Reply-To: <CAGKqTXUWhXJ7WphEOkSmrz9Zbq_vq8YOEa09hJDA5Sg9g9kkdg@mail.gmail.com> (Ami Fischman's message of "Sat, 28 Oct 2023 10:52:49 -0700")

Ami Fischman <ami@fischman.org> writes:

> Stepping back a bit from the specifics of Emacs and ratpoison, naively
> it seems unfortunate that X11 programs that have been working for
> decades should need to be modified to use similar-but-different APIs.
> Do you know whether the XInput2 people are aware of / at peace with
> this limitation, or is this something worth bringing up with them?

It's an immemorial and largely intentional design decision.  Core events
lack too much information for their transformation into extension events
to be possible.





      reply	other threads:[~2023-10-29  0:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 17:49 bug#66765: 30.0.50; Building emacs with xinput2 breaks receiving XSendEvent events Ami Fischman
2023-10-27  0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-27  6:04   ` Eli Zaretskii
2023-10-27  7:03     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-27  7:30       ` Eli Zaretskii
2023-10-27  7:38         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-27 10:27           ` Eli Zaretskii
2023-10-27 10:34             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-27 10:53               ` Eli Zaretskii
2023-10-27 10:57               ` Dmitry Gutov
2023-11-04  8:28     ` Eli Zaretskii
2023-11-04 10:25       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 11:04         ` Eli Zaretskii
     [not found] ` <handler.66765.D66765.169836681613748.notifdone@debbugs.gnu.org>
2023-10-27 17:37   ` bug#66765: closed (Re: bug#66765: 30.0.50; Building emacs with xinput2 breaks receiving XSendEvent events) Ami Fischman
2023-10-28  0:36     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 17:26       ` Ami Fischman
2023-10-28 17:52         ` Ami Fischman
2023-10-29  0:43           ` Po Lu 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=s0dh6ma9s2s.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66765@debbugs.gnu.org \
    --cc=ami@fischman.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).