From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: ami@fischman.org, 66765@debbugs.gnu.org
Subject: bug#66765: 30.0.50; Building emacs with xinput2 breaks receiving XSendEvent events
Date: Fri, 27 Oct 2023 13:53:08 +0300 [thread overview]
Message-ID: <83jzr8e3qj.fsf@gnu.org> (raw)
In-Reply-To: <87jzr8xsj3.fsf@yahoo.com> (message from Po Lu on Fri, 27 Oct 2023 18:34:56 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: 66765@debbugs.gnu.org, ami@fischman.org
> Date: Fri, 27 Oct 2023 18:34:56 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I guess it would be a good idea to have this information in PROBLEMS,
> > then.
>
> But that's tantamount to documenting the do's and don'ts of X
> development, since "xse" is nothing but a wrapper around an X request.
> It's a very slippery slope, though it's ultimately your call.
I'd rather we had this information in PROBLEMS, both for those who
consult that file and for us, when we need to help others to cope with
these issues.
In general, PROBLEMS should mention any problems with Emacs that
cannot be fixed in Emacs, preferably with workarounds, if we have
them.
next prev parent reply other threads:[~2023-10-27 10:53 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 [this message]
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
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=83jzr8e3qj.fsf@gnu.org \
--to=eliz@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).