From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: psainty@orcon.net.nz, 48025@debbugs.gnu.org
Subject: bug#48025: 28.0.50; Add an invocation option to inhibit native-compilation functionality
Date: Thu, 29 Apr 2021 14:33:17 +0000 [thread overview]
Message-ID: <xjfh7jpxis2.fsf@sdf.org> (raw)
In-Reply-To: <835z05dwk3.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Apr 2021 16:55:56 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: Phil Sainty <psainty@orcon.net.nz>, 48025@debbugs.gnu.org
>> Date: Wed, 28 Apr 2021 19:39:38 +0000
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> Could we rename any such variables so that everything to do with
>> >> native compilation includes the word "native"?
>> >
>> > Yes, I think it's a good idea. Perhaps also the commands in comp.el
>> > and even some non-interactive functions?
>>
>> I'll be happy to rename these functions if we come-up with a list.
>
> Here's a list I came up with:
>
> comp-limple-mode
> comp-speed
> comp-debug
> comp-verbose
> comp-always-compile
> comp-bootstrap-deny-list
> comp-never-optimize-functions
> comp-async-jobs-number
> comp-async-cu-done-functions
> comp-async-all-done-hook
> comp-async-env-modifier-form
> comp-async-report-warnings-errors
> comp-async-query-on-exit
> comp-native-driver-options
> comp-warning-on-missing-source
Thanks, should the renaming be comp-* to native-* ?
Andrea
next prev parent reply other threads:[~2021-04-29 14:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 5:52 bug#48025: 28.0.50; Add an invocation option to inhibit native-compilation functionality Phil Sainty
2021-04-26 12:08 ` Eli Zaretskii
2021-04-26 14:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-27 4:28 ` Phil Sainty
2021-04-27 13:34 ` Eli Zaretskii
2021-04-28 19:39 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 13:55 ` Eli Zaretskii
2021-04-29 14:33 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-04-29 15:05 ` Eli Zaretskii
2021-04-29 15:13 ` Eli Zaretskii
2021-04-29 15:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 15:45 ` Eli Zaretskii
2021-05-06 15:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-06 15:41 ` Eli Zaretskii
2022-06-30 13:08 ` Lars Ingebrigtsen
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=xjfh7jpxis2.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48025@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=psainty@orcon.net.nz \
/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.