From: chad <yandros@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: "Stefan Monnier" <monnier@iro.umontreal.ca>,
xenodasein@tutanota.de, "Björn Bidar" <bjorn.bidar@thaodan.de>,
emacs-devel@gnu.org
Subject: Re: Questions regarding PGTK, high-dpi font-rendering, new X11-Warning
Date: Mon, 5 Dec 2022 15:01:02 -0500 [thread overview]
Message-ID: <CAO2hHWZgPJtJfD4L2wA=HfKEOTA2gzom=DbbJ=G7baV5oM2pHA@mail.gmail.com> (raw)
In-Reply-To: <87r0xkt06d.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
On Wed, Nov 30, 2022 at 7:54 PM Po Lu <luangruo@yahoo.com> wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > What I read here is "we should move each GUI event loop into its own
> > thread" :-)
>
> That's not ok, as Xlib (used by both those toolkits, and also Emacs
> itself) is not thread safe.
>
> Even though it can be thread safe at first glance, having multiple
> threads work at the same time will mess up request serial tracking, and
> `x_error_catcher' and friends will stop working.
>
I'm not up to doing the work myself, and obviously I'm not asking anyone
else to do so, but I wonder if anyone has looked at moving emacs from Xlib
to XCB?
~Chad
[-- Attachment #2: Type: text/html, Size: 1124 bytes --]
next prev parent reply other threads:[~2022-12-05 20:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 22:38 Questions regarding PGTK, high-dpi font-rendering, new X11-Warning Björn Bidar
2022-11-27 0:48 ` Po Lu
2022-11-28 0:09 ` Björn Bidar
2022-11-28 1:17 ` Po Lu
2022-11-28 8:44 ` Björn Bidar
2022-11-28 11:41 ` Po Lu
2022-11-30 9:27 ` xenodasein--- via Emacs development discussions.
2022-11-30 10:13 ` Po Lu
2022-11-30 12:50 ` Stefan Monnier
2022-11-30 13:39 ` Po Lu
2022-11-30 16:50 ` Stefan Monnier
2022-12-01 0:52 ` Po Lu
2022-12-01 0:56 ` Stefan Monnier
2022-12-01 2:38 ` Po Lu
2022-12-01 5:24 ` Stefan Monnier
2022-12-01 6:45 ` Po Lu
2022-12-05 20:01 ` chad [this message]
2022-12-06 11:39 ` Po Lu
2022-12-06 13:05 ` xenodasein--- via Emacs development discussions.
2022-12-06 13:24 ` Po Lu
2022-12-01 10:25 ` Manuel Giraud
2022-12-01 12:44 ` Visuwesh
[not found] ` <87cz94vjgl.fsf@yahoo.com-NI70zP3----9>
2022-11-30 11:51 ` xenodasein--- via Emacs development discussions.
2022-11-30 13:37 ` Po Lu
2022-11-30 14:00 ` xenodasein--- via Emacs development discussions.
2022-11-30 14:09 ` Po Lu
2022-11-30 15:51 ` xenodasein--- via Emacs development discussions.
2022-12-01 0:49 ` Po Lu
2022-11-30 16:23 ` Eli Zaretskii
2022-11-30 16:56 ` xenodasein--- via Emacs development discussions.
2022-11-30 17:43 ` Eli Zaretskii
2022-12-12 23:52 ` Björn Bidar
2022-12-13 1:22 ` Po Lu
-- strict thread matches above, loose matches on Subject: below --
2022-11-29 6:33 Pedro Andres Aranda Gutierrez
2022-11-29 6:43 ` Po Lu
2022-11-29 9:36 ` Björn Bidar
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='CAO2hHWZgPJtJfD4L2wA=HfKEOTA2gzom=DbbJ=G7baV5oM2pHA@mail.gmail.com' \
--to=yandros@gmail.com \
--cc=bjorn.bidar@thaodan.de \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=xenodasein@tutanota.de \
/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).