From: Ihor Radchenko <yantar92@gmail.com>
To: reza <reza@housseini.me>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Extract toc from org file
Date: Tue, 27 Sep 2022 15:08:21 +0800 [thread overview]
Message-ID: <87sfkdnvkq.fsf@localhost> (raw)
In-Reply-To: <010201837db72cff-7a3d0b9f-8e0d-4a59-afeb-e3066b287e02-000000@eu-west-1.amazonses.com>
reza <reza@housseini.me> writes:
> I'm using org publish, but the sitemap does only collect the titles from
> org files but I want the complete toc of each file and as far as I
> undesrand this is not possible with sitemap?
You just need a custom :sitemap-function.
The default `org-publish-sitemap-default' flattens the hierarchy.
From the manual:
‘:sitemap-function’
Plug-in function to use for generation of the sitemap. It is
called with two arguments: the title of the site-map and a
representation of the files and directories involved in the project
as a nested list, which can further be transformed using
‘org-list-to-generic’, ‘org-list-to-subtree’ and alike. Default
value generates a plain list of links to all files in the project.
You may create a function similar to `org-publish-sitemap-default' but
using `org-list-to-subtree' instead of `org-list-to-org'
>> If you are exporting a single Org file that is using contents of
>> multiple #+include'd files, you can use the normal TOC generation as
>> described in 13.3 Table of Contents section of the Org manual.
>
> But this forces all the content into a single file, no?
Yes, it will. It is indeed not something you want in your use case.
--
Ihor Radchenko,
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:[~2022-09-27 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <100cb12a-b3f1-739a-84f1-847f5e86a8bc@housseini.me>
2022-09-26 11:53 ` Extract toc from org file reza
2022-09-26 15:21 ` Max Nikulin
2022-09-26 16:02 ` Max Nikulin
[not found] ` <bb5ed7b1-e281-39b1-d7e7-659a5317ad98@housseini.me>
2022-09-27 6:57 ` reza
2022-09-26 15:39 ` Juan Manuel Macías
[not found] ` <a5365480-d7b7-5015-7eb1-34e9bc215abf@housseini.me>
2022-09-27 6:54 ` reza
2022-09-27 1:28 ` Ihor Radchenko
[not found] ` <fa280d29-36db-8f94-c360-92366ebbeb64@housseini.me>
2022-09-27 6:51 ` reza
2022-09-27 7:08 ` Ihor Radchenko [this message]
[not found] ` <0ce13d8e-aea6-64af-86e5-da4f88be5d9c@housseini.me>
2022-09-27 8:19 ` reza
2022-09-27 12:47 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfkdnvkq.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=reza@housseini.me \
/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/org-mode.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).