From: Eli Zaretskii <eliz@gnu.org>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: luangruo@yahoo.com, 56487@debbugs.gnu.org
Subject: bug#56487: xgselect race condition leading to abort when USE_GTK not defined
Date: Tue, 12 Jul 2022 15:44:01 +0300 [thread overview]
Message-ID: <83tu7mxzzi.fsf@gnu.org> (raw)
In-Reply-To: <CA+G3_PNNha+YY8=P8DjknSxsc+jJ99+sBR4hrNusK9tf45_X9Q@mail.gmail.com> (message from Tom Gillespie on Mon, 11 Jul 2022 19:20:02 -0700)
> Cc: 56487@debbugs.gnu.org
> From: Tom Gillespie <tgbugs@gmail.com>
> Date: Mon, 11 Jul 2022 19:20:02 -0700
>
> > No, because we don't want the different GLib event dispatch behavior
> > outside of GTK with native input enabled.
>
> Ok, got it. I'll see if I can figure out an alternate solution with that
> constraint in mind.
TIA.
> Should I split out the release_select_lock change into a separate
> patch so that we can get that merged independent of a fix for the
> abort behavior?
Yes, I think that's a good idea.
next prev parent reply other threads:[~2022-07-12 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 21:05 bug#56487: xgselect race condition leading to abort when USE_GTK not defined Tom Gillespie
2022-07-11 1:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-11 2:50 ` Tom Gillespie
2022-07-11 3:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-11 3:40 ` Tom Gillespie
2022-07-11 10:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-11 16:09 ` Tom Gillespie
2022-07-12 2:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-12 2:20 ` Tom Gillespie
2022-07-12 12:44 ` Eli Zaretskii [this message]
2022-07-15 5:09 ` Tom Gillespie
2023-09-07 18:30 ` Stefan Kangas
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=83tu7mxzzi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56487@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=tgbugs@gmail.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).