From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ken Raeburn <raeburn@redhat.com>
Cc: 54715@debbugs.gnu.org
Subject: bug#54715: 28.0.92; crash when X server died
Date: Wed, 06 Apr 2022 08:43:43 +0800 [thread overview]
Message-ID: <87pmlv11og.fsf@yahoo.com> (raw)
In-Reply-To: <87sfqrs5vu.fsf@redhat.com> (Ken Raeburn's message of "Tue, 05 Apr 2022 15:10:45 -0400")
Ken Raeburn <raeburn@redhat.com> writes:
> To clarify: I used to run Emacs as a daemon (which would’ve been
> relevant if it meant there was another, invisible terminal frame), but
> apparently I stopped a while ago. That’s what I meant that my use of
> it had “fallen by the wayside”. (Perhaps I should’ve just not
> mentioned it.) So with both instances of the local display connection
> dead at the same time, there are no working frames left.
Ah, thanks for clarifying. I suppose there is no initial frame in that
case, so Eli's proposal about not calling redisplay_preserve_echo_area
seems reasonable to me.
prev parent reply other threads:[~2022-04-06 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 21:19 bug#54715: 28.0.92; crash when X server died Ken Raeburn
2022-04-05 1:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-05 12:16 ` Eli Zaretskii
2022-04-05 12:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-05 19:10 ` Ken Raeburn
2022-04-05 19:24 ` Eli Zaretskii
2022-04-06 0:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87pmlv11og.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54715@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=raeburn@redhat.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).