unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 59424@debbugs.gnu.org, akrl@sdf.org
Subject: bug#59424: bug#59358: 29.0.50; failing to load .eln for init file sets user-init-file to warnings.el
Date: Sun, 27 Nov 2022 22:26:55 +0200	[thread overview]
Message-ID: <837czgp2i8.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SSPZmgtcpWktvS4ucKVCZX5a9UyioR6vKmMWMsj-bH6gA@mail.gmail.com> (message from Juanma Barranquero on Sun, 27 Nov 2022 20:53:27 +0100)

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sun, 27 Nov 2022 20:53:27 +0100
> Cc: akrl@sdf.org, 59424@debbugs.gnu.org
> 
> This patch below is what I did, *just* to get comp not to complain about the "missing" .emacs.el.
> 
> Then something should be done to make it to compile .emacs, and I'm not sure where or how.

So the problem is not to find the source of .emacs.elc, the problem is also
to compile .emacs natively into .emacs.eln?  I though the problem was only
the former.

> I can't shake the feeling that I'm thrashing around and someone who knows the code could do it faster and
> cleaner.

I'm not sure a cleaner way exists, but I will let Andrea chime in.

Note that there's also maybe_defer_native_compilation.





  reply	other threads:[~2022-11-27 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 13:17 bug#59358: 29.0.50; failing to load .eln for init file sets user-init-file to warnings.el Juanma Barranquero
2022-11-18 14:24 ` 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 [this message]
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

  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=837czgp2i8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59424@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).