From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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 08:45:03 +0100 [thread overview]
Message-ID: <CAAeL0SRqCqaZiuVstr8=cvw78HUfB1tCW1h69AACVPxOZSaKfQ@mail.gmail.com> (raw)
In-Reply-To: <83a64od8nb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Fri, Nov 18, 2022 at 8:28 AM Eli Zaretskii <eliz@gnu.org> wrote:
> I think the call to gethash should only be done if the file has the
> .eln extension, otherwise you might have false positives.
Do you mean the hash comp-eln-to-el-h could have keys that match something
that doesn't end in .eln? Or that someone could've an init file with
extension .eln and matching one of the keys? Both seem extremely unlikely,
but ok.
> The file-exists-and-is-newer test is not relevant to the .eln case,
> because Emacs will not load a .eln file that is outdated wrt its
> source, and will not use a .eln file whose source is not available.
Ok. Easier, then.
[-- Attachment #2: Type: text/html, Size: 916 bytes --]
next prev parent reply other threads:[~2022-11-18 7:45 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
2022-11-18 7:27 ` Eli Zaretskii
2022-11-18 7:45 ` Juanma Barranquero [this message]
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='CAAeL0SRqCqaZiuVstr8=cvw78HUfB1tCW1h69AACVPxOZSaKfQ@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=59334@debbugs.gnu.org \
--cc=akrl@sdf.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).