From: Eli Zaretskii <eliz@gnu.org>
To: Tor Kringeland <tor.kringeland@ntnu.no>
Cc: akrl@sdf.org, stephen_leake@stephe-leake.org, emacs-devel@gnu.org
Subject: Re: disable automatic native-compilation?
Date: Tue, 12 Jul 2022 16:29:50 +0300 [thread overview]
Message-ID: <83k08ixxv5.fsf@gnu.org> (raw)
In-Reply-To: <m2y1wyfu5a.fsf@ntnu.no> (message from Tor Kringeland on Tue, 12 Jul 2022 11:27:29 +0000)
> From: Tor Kringeland <tor.kringeland@ntnu.no>
> CC: Stephen Leake <stephen_leake@stephe-leake.org>, emacs-devel
> <emacs-devel@gnu.org>
> Date: Tue, 12 Jul 2022 11:27:29 +0000
>
> Tor Kringeland <tor.kringeland@ntnu.no> writes:
>
> > I see. Maybe this could be mentioned explicitly in the manual? What
> > the manual says now is consistent with what you say, but when I read it
> > I got the impression that setting 'native-comp-speed' to -1 in
> > early-init.el would completely disable native compilation/wouldn't
> > generate the .eln files at all.
>
> Nevermind, it seems like Eli Zaretskii thought of the same and already
> changed the manual and doc string to be more explicit about this.
You are welcome ;-)
next prev parent reply other threads:[~2022-07-12 13:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 16:49 disable automatic native-compilation? Stephen Leake
2022-07-09 17:23 ` Eli Zaretskii
2022-07-10 15:10 ` Lynn Winebarger
2022-07-10 15:39 ` Eli Zaretskii
2022-07-10 18:32 ` Lynn Winebarger
2022-07-10 21:54 ` Ken Brown
2022-07-11 1:52 ` Ken Brown
2022-07-11 2:39 ` Lynn Winebarger
2022-07-11 13:37 ` Ken Brown
2022-07-11 13:56 ` Eli Zaretskii
2022-07-11 17:19 ` Ken Brown
2022-07-09 22:36 ` Tor Kringeland
2022-07-10 8:58 ` Philip Kaludercic
2022-07-11 12:54 ` Andrea Corallo
2022-07-12 11:04 ` Tor Kringeland
2022-07-12 11:27 ` Tor Kringeland
2022-07-12 13:29 ` Eli Zaretskii [this message]
2022-08-06 15:32 ` Lynn Winebarger
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=83k08ixxv5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.org \
--cc=tor.kringeland@ntnu.no \
/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.