unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Arsen Arsenović" <arsen@aarsen.me>,
	dgutov@yandex.ru, spwhitton@spwhitton.name, emacs-devel@gnu.org
Subject: Re: Qt can now survive Wayland compositor restarts
Date: Sat, 11 Mar 2023 15:35:32 +0800	[thread overview]
Message-ID: <87a60jeo57.fsf@yahoo.com> (raw)
In-Reply-To: <83o7ozydhk.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 11 Mar 2023 09:05:27 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Arsen Arsenović <arsen@aarsen.me>
>> Cc: Sean Whitton <spwhitton@spwhitton.name>, emacs-devel@gnu.org
>> Date: Fri, 10 Mar 2023 23:17:17 +0100
>> 
>> I was considering trying to do a separation of UI and Elisp threads as a
>> solution, but, seeing this happen makes me think a Qt port is easier.
>> 
>> I'd still like opinions on the former idea, though.  It might be
>> worthwhile, but I am operating with little knowledge of that part of the
>> code-base, so I'm unsure if there's some deeper reason behind this not
>> being the case today.
>
> FYI: the MS-Windows build of Emacs uses a separate thread for input
> and UI.

Likewise for the Haiku and Android ports, FWIW.



  reply	other threads:[~2023-03-11  7:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 16:31 Qt can now survive Wayland compositor restarts Sean Whitton
2023-03-10 21:46 ` Dmitry Gutov
2023-03-10 22:17   ` Arsen Arsenović
2023-03-11  2:06     ` Björn Bidar
2023-03-11  7:05     ` Eli Zaretskii
2023-03-11  7:35       ` Po Lu [this message]
2023-03-11 10:58         ` Arsen Arsenović
2023-03-11 11:12           ` Po Lu
2023-03-11 11:23             ` Arsen Arsenović
2023-03-11 11:37               ` Po Lu
2023-03-11 12:25                 ` Arsen Arsenović
2023-03-11 12:33                   ` Po Lu
2023-03-11 12:36                     ` Arsen Arsenović
2023-03-12  1:41               ` Madhu
2023-03-10 23:46   ` Po Lu
2023-03-10 23:48 ` Po Lu

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=87a60jeo57.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=arsen@aarsen.me \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=spwhitton@spwhitton.name \
    /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).