From: Po Lu <luangruo@yahoo.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: Eli Zaretskii <eliz@gnu.org>,
dgutov@yandex.ru, spwhitton@spwhitton.name,
emacs-devel@gnu.org
Subject: Re: Qt can now survive Wayland compositor restarts
Date: Sat, 11 Mar 2023 19:37:22 +0800 [thread overview]
Message-ID: <871qlvecy5.fsf@yahoo.com> (raw)
In-Reply-To: <86a60j1q55.fsf@aarsen.me> ("Arsen Arsenović"'s message of "Sat, 11 Mar 2023 12:23:28 +0100")
Arsen Arsenović <arsen@aarsen.me> writes:
> It would be indeed.
>
> The likelihood of crashes would be lowered if the display server event
> loop is not kept busy by the Elisp interpreter, though, which is why a
> separate thread would help (for instance, I suspect that the reason I
> see crashes when sending mail on occasion is because smtpmail blocks the
> main thread and a bunch of mouse events get queued up in the meanwhile,
> causing libwayland to give up).
If the display server crashes, the connection is closed, and GDK gives
up when it calls `wl_display_flush' at some point and gets SIGPIPE.
It's not related to events being queued up or whatever.
> In either case, the better fix would be teaching GTK not to do silly
> things on error conditions, and instead consult the user, but I'm not
> sure how doable that is.
Very easy, as was proven when this feature actually worked as intended
sometime during the 2.14 series. It's just that the GTK developers need
their power fix and refuse to actually fix the problem, because ``only
Emacs needs this fixed.''
next prev parent reply other threads:[~2023-03-11 11:37 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
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 [this message]
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=871qlvecy5.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).