From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 56528@debbugs.gnu.org, visuweshm@gmail.com
Subject: bug#56528: 29.0.50; Emacs lucid segfaults when X dies
Date: Thu, 14 Jul 2022 08:36:29 +0300 [thread overview]
Message-ID: <837d4guug2.fsf@gnu.org> (raw)
In-Reply-To: <874jzkv878.fsf@yahoo.com> (message from Po Lu on Thu, 14 Jul 2022 08:39:23 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Visuwesh <visuweshm@gmail.com>, 56528@debbugs.gnu.org
> Date: Thu, 14 Jul 2022 08:39:23 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Btw, what do we expect Emacs to do in this scenario? If the X server
> > is killed, Emacs cannot display anything, so why an abort is not TRT?
> > What practically interesting use case does this emulate?
>
> It should just print an error message and die with a specific exit code,
> without printing a giant backtrace to stdout.
Print an error message where?
> Would binding `inhibit-redisplay' around the call to Fkill_emacs be a
> reasonable solution?
No, because that's not what inhibit-redisplay is for.
I think the right solution for this use case is to add a new command
that deletes all client frames. We are talking about a user who
intentionally kills the X server, so the ability to conveniently
delete all the frames except the daemon frame will (or should) allow
Emacs to survive the traumatic event.
next prev parent reply other threads:[~2022-07-14 5:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 4:32 bug#56528: 29.0.50; Emacs lucid segfaults when X dies visuweshm
2022-07-13 10:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 11:05 ` Visuwesh
2022-07-13 12:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 13:06 ` Visuwesh
2022-07-13 13:13 ` Eli Zaretskii
2022-07-13 13:15 ` Eli Zaretskii
2022-07-13 13:23 ` Visuwesh
2022-07-13 13:49 ` Eli Zaretskii
2022-07-13 14:18 ` Visuwesh
2022-07-13 17:11 ` Eli Zaretskii
2022-07-13 17:18 ` Eli Zaretskii
2022-07-13 17:29 ` Visuwesh
2022-07-13 17:54 ` Eli Zaretskii
2022-07-13 17:20 ` Visuwesh
2022-07-13 17:50 ` Eli Zaretskii
2022-07-14 1:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:41 ` Eli Zaretskii
2022-07-14 6:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 7:18 ` Eli Zaretskii
2022-07-14 1:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:39 ` Eli Zaretskii
2022-07-14 6:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 7:18 ` Eli Zaretskii
2022-07-14 7:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-15 16:17 ` Andrés Ramírez
2022-07-16 3:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:36 ` Eli Zaretskii [this message]
2022-07-14 6:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 3:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 4:24 ` Visuwesh
2022-07-14 4:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:37 ` Visuwesh
2022-07-14 6:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837d4guug2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56528@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=visuweshm@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.