From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: germanp82@hotmail.com, 57627@debbugs.gnu.org,
Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#57627: 29.0.50; [native-compilation] cl-loaddefs.el recompiled on startup
Date: Mon, 17 Oct 2022 10:49:23 +0200 [thread overview]
Message-ID: <87bkqahm24.fsf@gnus.org> (raw)
In-Reply-To: <xjfo7uavql0.fsf@ma.sdf.org> (Andrea Corallo's message of "Mon, 17 Oct 2022 07:47:55 +0000")
Andrea Corallo <akrl@sdf.org> writes:
> Why not to use `native-comp-deferred-compilation-deny-list' instead of
> adding `native-comp--no-native-compile'?
`native-comp-deferred-compilation-deny-list' is a user option, so it
shouldn't be used for programmatic updates like this. (I.e., a user may
overwrite the automatic updates.)
> If we can't use `native-comp-deferred-compilation-deny-list' maybe we
> should rename `native-comp--no-native-compile' to
> `comp--no-native-compile'? This is the scheme we used for variables
> that are not supposed to be manipulated by the user.
Right; now done, and change pushed to master.
next prev parent reply other threads:[~2022-10-17 8:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 11:38 bug#57627: 29.0.50; [native-compilation] cl-loaddefs.el recompiled on startup German Pacenza
2022-09-06 15:02 ` Lars Ingebrigtsen
2022-09-06 15:46 ` German Pacenza
2022-09-06 15:51 ` Lars Ingebrigtsen
2022-09-06 16:33 ` Andrea Corallo
2022-09-06 16:41 ` Eli Zaretskii
2022-09-06 19:23 ` Andrea Corallo
2022-09-06 20:40 ` Lars Ingebrigtsen
2022-09-07 2:33 ` Eli Zaretskii
2022-09-07 12:47 ` Lars Ingebrigtsen
2022-09-07 13:01 ` German Pacenza
2022-09-07 13:06 ` Lars Ingebrigtsen
2022-09-07 13:41 ` Lars Ingebrigtsen
2022-09-07 13:08 ` Eli Zaretskii
2022-09-07 13:10 ` Lars Ingebrigtsen
2022-09-07 18:06 ` Andrea Corallo
2022-09-08 11:57 ` Lars Ingebrigtsen
2022-09-09 12:57 ` Andrea Corallo
2022-09-09 17:09 ` Lars Ingebrigtsen
2022-09-09 19:03 ` Andrea Corallo
2022-09-10 4:33 ` Lars Ingebrigtsen
2022-09-10 4:38 ` Lars Ingebrigtsen
2022-10-14 10:53 ` Lars Ingebrigtsen
2022-10-14 19:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 10:13 ` Lars Ingebrigtsen
2022-10-15 14:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 8:21 ` Lars Ingebrigtsen
2022-10-17 7:47 ` Andrea Corallo
2022-10-17 8:49 ` Lars Ingebrigtsen [this message]
2022-10-17 8:52 ` Andrea Corallo
2022-10-17 9:06 ` Eli Zaretskii
2022-10-17 9:13 ` Lars Ingebrigtsen
2022-10-17 11:59 ` Arash Esbati
2022-10-17 12:01 ` Lars Ingebrigtsen
2022-10-17 12:09 ` Arash Esbati
2022-10-17 12:21 ` Lars Ingebrigtsen
2022-10-17 12:31 ` Lars Ingebrigtsen
2022-10-17 12:53 ` Arash Esbati
2022-10-17 12:59 ` German Pacenza
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=87bkqahm24.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57627@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=germanp82@hotmail.com \
--cc=monnier@iro.umontreal.ca \
/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).