From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 59334@debbugs.gnu.org, akrl@sdf.org
Subject: bug#59334: 29.0.50; loading native-compiled init file sets user-init-file to .eln
Date: Fri, 18 Nov 2022 09:19:00 +0200 [thread overview]
Message-ID: <83bkp4d923.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SSdRjnXFbhUM98kON-s84AP2C=mTnx04czrR11Nj9-NnQ@mail.gmail.com> (message from Juanma Barranquero on Fri, 18 Nov 2022 03:25:34 +0100)
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 18 Nov 2022 03:25:34 +0100
> Cc: Andrea Corallo <akrl@sdf.org>, 59334@debbugs.gnu.org
>
> If you use ~/.emacs instead of ~.emacs.d/init.el, and happen to compile .emacs, Emacs loads .emacs.elc
> (as it has always done), but the native compiler does *not* know how to compile it (because it does not know
> how to locate its source), so it gives a warning:
>
> 022-11-18 02:54:01+0100 Warning (comp): Cannot look up eln file as no source file was found for
> d:/Home/.emacs.elc
>
> and then it assigns the user-init-file to warnings.el!
>
> ELISP> user-init-file
> "d:/Home/.emacs.d/native/29.0.50-a4a10996/warnings-28e75f4d-02da775e.eln"
>
> which, if my patch is installed, gets converted to its source file:
>
> ELISP> user-init-file
> "d:/Devel/emacs/repo/trunk/lisp/emacs-lisp/warnings.el"
>
> So this is a double bug for anyone compiling their .emacs: they will always get a warning, and an erroneous
> user-init-file.
>
> Do you want me to file this as a separate bug?
Yes, please.
next prev parent reply other threads:[~2022-11-18 7:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 9:28 bug#59334: 29.0.50; loading native-compiled init file sets user-init-file to .eln Juanma Barranquero
2022-11-17 12:07 ` Eli Zaretskii
2022-11-17 13:30 ` Juanma Barranquero
2022-11-17 14:00 ` Eli Zaretskii
2022-11-17 20:04 ` Andrea Corallo
2022-11-17 20:09 ` Eli Zaretskii
2022-11-18 2:25 ` Juanma Barranquero
2022-11-18 2:56 ` Juanma Barranquero
2022-11-18 3:03 ` Juanma Barranquero
2022-11-18 7:50 ` Eli Zaretskii
2022-11-18 7:19 ` Eli Zaretskii [this message]
2022-11-18 7:27 ` Eli Zaretskii
2022-11-18 7:45 ` Juanma Barranquero
2022-11-18 8:46 ` Eli Zaretskii
2022-11-18 9:05 ` Juanma Barranquero
2022-11-18 9:08 ` Juanma Barranquero
2022-11-18 12:33 ` Eli Zaretskii
2022-11-18 12:40 ` Juanma Barranquero
2022-11-18 12:50 ` Eli Zaretskii
2022-11-18 13:03 ` Juanma Barranquero
2022-11-18 20:02 ` Andrea Corallo
2022-11-18 10:39 ` Andrea Corallo
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=83bkp4d923.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59334@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=lekktu@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 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).