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 20:33:42 +0800 [thread overview]
Message-ID: <87wn3ncvrt.fsf@yahoo.com> (raw)
In-Reply-To: <86edpvzd09.fsf@aarsen.me> ("Arsen Arsenović"'s message of "Sat, 11 Mar 2023 13:25:05 +0100")
Arsen Arsenović <arsen@aarsen.me> writes:
> Yes, it's indeed not related in the display server crash case. That is
> not the case that concerns me in this instance, though.
>
> The display server keeps working just fine when I see GTK call _exit.
>
> You can simulate this by starting Emacs, suspending it, resizing the
> window a bunch and clicking around, and then unsuspending it:
>
> ~$ emacs
> ^Z
> [1]+ Stopped emacs
> << Some mouse/resize spam here for a few seconds >>
> ~ 148 $ fg
> emacs
> Gdk-Message: 13:26:40.087: Lost connection to Wayland compositor.
> ~ 1 $
Well, in this case the compositor has still closed the connection, so
the consequences are the same.
The Lisp interpreter should periodically poll for input and also read
input as it becomes available, so this should not be a problem with
long-running Lisp code. If it is, please report a bug. Thanks.
next prev parent reply other threads:[~2023-03-11 12:33 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
2023-03-11 12:25 ` Arsen Arsenović
2023-03-11 12:33 ` Po Lu [this message]
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=87wn3ncvrt.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).