From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Kyle Meyer <kyle@kyleam.com>, Robert Pluim <rpluim@gmail.com>,
emacs-devel@gnu.org
Subject: Re: master c86995d07e9: Enable code block evaluation when generating .org manuals
Date: Mon, 17 Jun 2024 11:46:55 +0000 [thread overview]
Message-ID: <87wmmnbxlc.fsf@localhost> (raw)
In-Reply-To: <CADwFkm=DTsEfj_ZaSu62_8r-02_bxrMQik9jBhCk-whNrS7JJQ@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
>> May you please point me to where in the Makefiles you do the
>> pre-generation you are referring to?
>
> Running the `admin/update_autogen` script results in commits like this
> one:
>
> commit 1ea3b369021c90701c634c512426f75ce1291d77
> Author: Eli Zaretskii <eliz@gnu.org>
> Date: Sat Mar 9 04:24:30 2024 -0500
>
> Auto-commit of loaddefs files.
Thanks!
I am now looking into that script, and into doc/misc/Makefile.
I can see two approaches wrt to the Makefile:
1. Implement a separate Makefile target to generate org.org version with
all the necessary code blocks inside evaluated, so that there is no
need to redo it during make doc.
2. (simpler) Just reuse the existing .org->.texi target and run the full
.texi generation from admin/update_autogen script itself.
The second option is less work and also ultimately shorter build times
as there will be no need to arrange Org mode compilation, and
.org->.texi conversion.
What do you think about such approach?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-06-17 11:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171767737644.19678.784876979840850798@vcs2.savannah.gnu.org>
[not found] ` <20240606123616.DE7C9C1F9EF@vcs2.savannah.gnu.org>
2024-06-06 14:31 ` master c86995d07e9: Enable code block evaluation when generating .org manuals Robert Pluim
2024-06-07 2:39 ` Kyle Meyer
2024-06-07 8:50 ` Stefan Kangas
2024-06-09 17:55 ` Ihor Radchenko
2024-06-09 18:26 ` Stefan Kangas
2024-06-09 18:45 ` Ihor Radchenko
2024-06-09 19:19 ` Stefan Kangas
2024-06-15 14:38 ` Ihor Radchenko
2024-06-15 14:47 ` Stefan Kangas
2024-06-17 11:46 ` Ihor Radchenko [this message]
2024-06-18 19:37 ` Stefan Kangas
2024-06-07 3:54 ` Po Lu
2024-06-07 4:26 ` tomas
2024-06-07 5:13 ` Po Lu
2024-06-07 6:38 ` tomas
2024-06-07 6:42 ` Eli Zaretskii
2024-06-07 7:38 ` Robert Pluim
2024-06-07 11:01 ` Eli Zaretskii
2024-06-07 11:17 ` Po Lu
2024-06-07 8:12 ` tomas
2024-06-09 2:16 ` Richard Stallman
2024-06-09 18:12 ` Ihor Radchenko
2024-06-09 18:27 ` Eli Zaretskii
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=87wmmnbxlc.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=rpluim@gmail.com \
--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.