From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: acm@muc.de, stefankangas@gmail.com, 58224@debbugs.gnu.org
Subject: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file"
Date: Sun, 02 Oct 2022 14:04:08 +0300 [thread overview]
Message-ID: <83y1ty1o7r.fsf@gnu.org> (raw)
In-Reply-To: <YzlrYIYp+j1z2mmC@ACM> (message from Alan Mackenzie on Sun, 2 Oct 2022 10:43:44 +0000)
> Date: Sun, 2 Oct 2022 10:43:44 +0000
> Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org, acm@muc.de
> From: Alan Mackenzie <acm@muc.de>
>
> > Instead of inventing a new value that overrides the non-nil value, why
> > not simply reset the variable to nil?
>
> force-load-messages is nil by default, and currently isn't used at all
> by Emacs. It seems to be a pure debugging variable.
>
> The NOMESSAGE argument to Fload when non-nil, causes the unwanted
> message:
>
> Source file `foo.el' newer than byte-compiled file; using older file
>
> .. When NOMESSAGE is nil, we get instead
>
> Loading foo.elc (compiled; note, source file is newer)...
>
> .. Whichever setting of NOMESSAGE and force-load-messages we use, we get
> one of the above messages displayed. So, I'm proposing using a new
> value 'never for force-load-messages to mean display neither of these
> messages.
I don't want to complicate the public Lisp API because we have a
singular situation at some point of the bootstrap, and for minor
aesthetic reasons at that; that is the tail wagging the dog. So let's
fix this more subtly.
How about recognizing (inside Fload) a specific time stamp of the
older file we use (we set it to the beginning of the Epoch, right?),
and suppressing the message in that case?
next prev parent reply other threads:[~2022-10-02 11:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 14:15 bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Stefan Kangas
2022-10-01 14:29 ` Lars Ingebrigtsen
2022-10-01 14:50 ` Eli Zaretskii
2022-10-01 16:10 ` Stefan Kangas
2022-10-01 18:11 ` Alan Mackenzie
2022-10-01 21:15 ` Alan Mackenzie
2022-10-02 5:59 ` Eli Zaretskii
2022-10-02 10:43 ` Alan Mackenzie
2022-10-02 11:04 ` Eli Zaretskii [this message]
2022-10-02 11:32 ` Alan Mackenzie
2022-10-02 15:38 ` Alan Mackenzie
2022-10-02 15:54 ` Eli Zaretskii
2022-10-02 16:46 ` Alan Mackenzie
2022-10-02 17:07 ` Eli Zaretskii
2022-10-02 20:37 ` Alan Mackenzie
2022-10-02 21:29 ` Stefan Kangas
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=83y1ty1o7r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58224@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=stefankangas@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 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.