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: Sun, 09 Jun 2024 17:55:18 +0000 [thread overview]
Message-ID: <874ja22e7t.fsf@localhost> (raw)
In-Reply-To: <CADwFkmm5ChbCH3fnxfmnT2sH=tTY8mDnN2DTCKkZksqygsw_NQ@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
> Kyle Meyer <kyle@kyleam.com> writes:
>
>> As mentioned by Ihor (+cc) in bug#71394, this change is needed before
>> syncing the latest Org release to the Emacs tree due to Org's 715148131
>> (org-manual: Automatically generate export option list, 2023-07-31).
>
> Does it really need to generated automatically on every build, or can it
> be handled in some other way? For example, we pre-generate our loaddefs
> files and commit the result.
Preferably, every build, I think.
What we do in Org mode manual is examining an Elisp variable and build a
table summarizing its values. If that variable changes in the code, the
manual should reflect this change.
--
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-09 17:55 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 [this message]
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
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
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=874ja22e7t.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 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).