From: Gregory Heytings <gregory@heytings.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: eliz@gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: emacs.pdmp not always rebuilt
Date: Mon, 04 Oct 2021 14:19:52 +0000 [thread overview]
Message-ID: <6c69780538bd3f6a7369@heytings.org> (raw)
In-Reply-To: <CADwFkmn3PnzmT+pRi4RVGNnz7vutaQBtaS2QRmB9XLMdGQBZDA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 299 bytes --]
>> I think avoiding the call if the function is not available is the
>> cleanest solution, one that we use elsewhere in Emacs in similar cases.
>
> That sounds reasonable, yes.
>
And here is the patch. As I just said, I'm not entirely convinced that
it's better, but it isn't much worse either.
[-- Attachment #2: Type: text/x-diff, Size: 983 bytes --]
From 0d7dbb4801d914be00ac9b9685fdb5c7b3d619ab Mon Sep 17 00:00:00 2001
From: Gregory Heytings <gregory@heytings.org>
Date: Mon, 4 Oct 2021 14:13:46 +0000
Subject: [PATCH] Fix problem with outputting error messages while dumping
Emacs better
* src/print.c (print_error_message): Don't call substitute-command-keys
when it isn't bound.
---
src/print.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/print.c b/src/print.c
index ef01738436..221e7b8c2a 100644
--- a/src/print.c
+++ b/src/print.c
@@ -941,7 +941,7 @@ print_error_message (Lisp_Object data, Lisp_Object stream, const char *context,
else
{
Lisp_Object error_conditions = Fget (errname, Qerror_conditions);
- if (will_bootstrap_p () || will_dump_p ())
+ if (NILP (Fboundp (Qsubstitute_command_keys)))
errmsg = Fget (errname, Qerror_message);
else
errmsg = call1 (Qsubstitute_command_keys, Fget (errname, Qerror_message));
--
2.33.0
next prev parent reply other threads:[~2021-10-04 14:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 12:41 emacs.pdmp not always rebuilt Lars Ingebrigtsen
2021-10-03 12:53 ` Eli Zaretskii
2021-10-03 13:10 ` Lars Ingebrigtsen
2021-10-03 14:35 ` Stefan Monnier
2021-10-03 14:38 ` Lars Ingebrigtsen
2021-10-03 23:27 ` Gregory Heytings
2021-10-04 0:45 ` Stefan Kangas
2021-10-04 2:28 ` Eli Zaretskii
2021-10-04 8:57 ` Gregory Heytings
2021-10-04 9:19 ` Lars Ingebrigtsen
2021-10-04 11:14 ` Stefan Kangas
2021-10-04 12:53 ` Eli Zaretskii
2021-10-04 12:50 ` Eli Zaretskii
2021-10-04 13:05 ` Gregory Heytings
2021-10-04 13:25 ` Gregory Heytings
2021-10-04 13:37 ` Eli Zaretskii
2021-10-04 14:18 ` Gregory Heytings
2021-10-04 14:34 ` Eli Zaretskii
2021-10-04 16:02 ` Gregory Heytings
2021-10-04 16:56 ` Eli Zaretskii
2021-10-04 13:30 ` Eli Zaretskii
2021-10-04 14:03 ` Stefan Kangas
2021-10-04 14:19 ` Gregory Heytings [this message]
2021-10-04 15:10 ` Eli Zaretskii
2021-10-03 14:52 ` Eli Zaretskii
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=6c69780538bd3f6a7369@heytings.org \
--to=gregory@heytings.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.