From: Fejfighter <fejfighter@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55861@debbugs.gnu.org
Subject: bug#55861: [PATCH] Update native-comp error message to reflect variable change
Date: Thu, 9 Jun 2022 16:06:26 +1000 [thread overview]
Message-ID: <CALohuRAituJXggBF5Lp=6cgWii+2B7_Wa-coBkmjGcnLLUvM2w@mail.gmail.com> (raw)
In-Reply-To: <83ilpa4d2p.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 379 bytes --]
On Thu, Jun 9, 2022 at 3:32 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Fejfighter <fejfighter@gmail.com>
> > Date: Thu, 9 Jun 2022 10:17:48 +1000
> >
> > Updates a Native-compilation error message to make debugging user init
> > files much easier.
> >
> > The referenced variable got renamed sometime during integration, this
> just
> > got missed somehow.
>
> ENOPATCH
>
[-- Attachment #1.2: Type: text/html, Size: 774 bytes --]
[-- Attachment #2: 0001-Update-error-message-to-reflect-variable-rename.patch --]
[-- Type: text/x-patch, Size: 769 bytes --]
From 940357a6ec07527609784d7d5515bfa9b45096d0 Mon Sep 17 00:00:00 2001
From: Jeff Walsh <fejfighter@gmail.com>
Date: Thu, 9 Jun 2022 10:02:01 +1000
Subject: [PATCH] Update error message to reflect variable rename
* src/comp.c (Fcomp_el_to_eln_filename): update mesage
---
src/comp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/comp.c b/src/comp.c
index 97bc6a5f9d..05d9fed448 100644
--- a/src/comp.c
+++ b/src/comp.c
@@ -4466,7 +4466,7 @@ DEFUN ("comp-el-to-eln-filename", Fcomp_el_to_eln_filename,
}
if (NILP (base_dir))
error ("Cannot find suitable directory for output in "
- "`comp-native-load-path'.");
+ "`native-comp-eln-load-path'.");
}
if (!file_name_absolute_p (SSDATA (base_dir)))
--
2.36.1
next prev parent reply other threads:[~2022-06-09 6:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 0:17 bug#55861: [PATCH] Update native-comp error message to reflect variable change Fejfighter
2022-06-09 5:31 ` Eli Zaretskii
2022-06-09 6:06 ` Fejfighter [this message]
2022-06-09 6:37 ` Andrea Corallo
2022-06-09 7:06 ` Eli Zaretskii
2022-06-09 8:14 ` Andrea Corallo
2022-06-09 6: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
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='CALohuRAituJXggBF5Lp=6cgWii+2B7_Wa-coBkmjGcnLLUvM2w@mail.gmail.com' \
--to=fejfighter@gmail.com \
--cc=55861@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).