all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: 59358@debbugs.gnu.org
Subject: bug#59358: 29.0.50; failing to load .eln for init file sets user-init-file to warnings.el
Date: Fri, 18 Nov 2022 14:17:36 +0100	[thread overview]
Message-ID: <CAAeL0SSHajgzyH7xF34wApcz7Sa0nHEkh7GRDA+jW8QpRmtQxQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

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 the native-compiled warnings.el,

"d:/Home/.emacs.d/native/29.0.50-a4a10996/warnings-28e75f4d-02da775e.eln"

which now, with the fix for bug#59334, ends up pointing to warnings.el:

ELISP> user-init-file
"d:/Devel/emacs/repo/trunk/lisp/emacs-lisp/warnings.el"

[-- Attachment #2: Type: text/html, Size: 1569 bytes --]

             reply	other threads:[~2022-11-18 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 13:17 Juanma Barranquero [this message]
2022-11-18 14:24 ` bug#59358: 29.0.50; failing to load .eln for init file sets user-init-file to warnings.el Eli Zaretskii
2022-11-19  9:13   ` Juanma Barranquero
2022-11-19 10:21     ` Eli Zaretskii
2022-11-20 18:59       ` Andrea Corallo
2022-11-27 19:01   ` bug#59424: " Juanma Barranquero
2022-11-27 19:26     ` Eli Zaretskii
2022-11-27 19:53       ` Juanma Barranquero
2022-11-27 20:26         ` Eli Zaretskii
2022-11-27 20:29           ` Juanma Barranquero
2022-11-28 13:58           ` Andrea Corallo
2022-11-20 22:14 ` bug#59358: Juanma Barranquero

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=CAAeL0SSHajgzyH7xF34wApcz7Sa0nHEkh7GRDA+jW8QpRmtQxQ@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=59358@debbugs.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 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.