From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58509@debbugs.gnu.org, akrl@sdf.org
Subject: bug#58509: 29.0.50; Synchronous nativecomp
Date: Fri, 14 Oct 2022 14:20:24 +0200 [thread overview]
Message-ID: <874jw6a96f.fsf@gnus.org> (raw)
In-Reply-To: <83edva8v1j.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Oct 2022 15:11:04 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> The original report said:
>
>> I thought I'd open a bug report for something I mentioned elsewhere: It
>> should be possible for --batch Emacsen to do native compilation.
> [...]
>> So I'd like to be able to say "emacs --batch --native-compile -l ..." or
>> something along those lines.
>
> So it seemed to me like being able to say
>
> emacs --batch -f batch-native-compile FILE...
>
> is what you want? If not, please tell what I missed in the original
> report.
You missed that the --native-compile there is in no way related to the
-l that follows. I.e., for instance:
emacs --batch --native-compile --eval '(gnus)'
should native-compile all parts of running Gnus.
next prev parent reply other threads:[~2022-10-14 12:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 10:38 bug#58509: 29.0.50; Synchronous nativecomp Lars Ingebrigtsen
2022-10-14 10:53 ` Eli Zaretskii
2022-10-14 10:56 ` Lars Ingebrigtsen
2022-10-14 11:04 ` Eli Zaretskii
2022-10-14 11:13 ` Lars Ingebrigtsen
2022-10-14 11:49 ` Eli Zaretskii
2022-10-14 11:51 ` Lars Ingebrigtsen
2022-10-14 11:53 ` Eli Zaretskii
2022-10-14 11:59 ` Lars Ingebrigtsen
2022-10-14 12:11 ` Eli Zaretskii
2022-10-14 12:20 ` Lars Ingebrigtsen [this message]
2022-10-14 12:54 ` Eli Zaretskii
2022-10-14 12:59 ` Lars Ingebrigtsen
2022-10-14 13:05 ` Eli Zaretskii
2022-10-14 13:15 ` Lars Ingebrigtsen
2022-10-14 21:40 ` Andrea Corallo
2022-10-15 6:45 ` Eli Zaretskii
2022-10-15 9:22 ` Lars Ingebrigtsen
2022-10-15 16:29 ` Andrea Corallo
2022-10-16 8:50 ` Lars Ingebrigtsen
2022-10-17 7:52 ` Andrea Corallo
2022-10-17 11:20 ` Lars Ingebrigtsen
2022-10-17 11:57 ` Lars Ingebrigtsen
2022-10-17 13:41 ` Eli Zaretskii
2022-10-17 19:30 ` Lars Ingebrigtsen
2022-10-18 13:43 ` Eli Zaretskii
2022-10-18 13:55 ` Andrea Corallo
2022-10-18 18:15 ` Lars Ingebrigtsen
2022-10-19 19:06 ` Andrea Corallo
2022-10-18 18:45 ` Eli Zaretskii
2022-10-19 19:02 ` Andrea Corallo
2022-10-19 19:11 ` Eli Zaretskii
2022-10-19 19:31 ` Andrea Corallo
2022-10-20 6:43 ` Eli Zaretskii
2022-10-20 7:23 ` Andrea Corallo
2022-10-20 8:06 ` Eli Zaretskii
2022-10-23 10:51 ` Andrea Corallo
2022-10-23 11:43 ` Eli Zaretskii
2022-10-23 12:10 ` Andrea Corallo
2022-10-25 19:54 ` Andrea Corallo
2022-10-26 2:30 ` Eli Zaretskii
2022-10-26 6:40 ` Andrea Corallo
2022-10-18 18:14 ` Lars Ingebrigtsen
2022-10-18 18:32 ` Eli Zaretskii
2022-10-18 18:39 ` Eli Zaretskii
2022-10-19 9:06 ` 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=874jw6a96f.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58509@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 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.