From: Ami Fischman <ami@fischman.org>
To: 66765@debbugs.gnu.org
Subject: bug#66765: closed (Re: bug#66765: 30.0.50; Building emacs with xinput2 breaks receiving XSendEvent events)
Date: Fri, 27 Oct 2023 10:37:13 -0700 [thread overview]
Message-ID: <CAGKqTXUTKN8Jv7pSDUQhz=wEmiW-9K-urHPCxEkUoZ_rsW3c5w@mail.gmail.com> (raw)
In-Reply-To: <handler.66765.D66765.169836681613748.notifdone@debbugs.gnu.org>
Thanks for following up, all.
> > The OP talked specifically about ratpoison.
> ratpoison doesn't send events to Emacs itself.
This is incorrect. I only included the `xse` invocation to provide
readers of the bug who do not use ratpoison normally a way to
reproduce the issue. Ratpoison _does_ call XSendEvent directly, e.g.
at https://git.savannah.nongnu.org/cgit/ratpoison.git/tree/src/actions.c?h=v1.4.9#n1414
> It is easily replaced with "xdotool" or suchlike.
For the record, xdotool (version 3.20160805.1) fails similarly to xse
and ratpoison when I try to use it like this:
xdotool key --window 0x36000d4 ctrl+a
(window ID of HEAD emacs with xinput2 results in a no-op, window ID of
emacs without xinput2 correctly receives a C-a event)
I'm curious if you have an example invocation you can share that does
result in a C-a being injected to an emacs build with XInput2 support.
next prev parent reply other threads:[~2023-10-27 17:37 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 ` Ami Fischman [this message]
2023-10-28 0:36 ` bug#66765: closed (Re: bug#66765: 30.0.50; Building emacs with xinput2 breaks receiving XSendEvent events) 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
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='CAGKqTXUTKN8Jv7pSDUQhz=wEmiW-9K-urHPCxEkUoZ_rsW3c5w@mail.gmail.com' \
--to=ami@fischman.org \
--cc=66765@debbugs.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 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).