emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: index for HTML export
Date: Thu, 14 Jul 2022 09:18:07 +0200	[thread overview]
Message-ID: <87bkts5fio.fsf@wi.uni-muenster.de> (raw)
In-Reply-To: <87sfn4yy71.fsf@ucl.ac.uk> (Eric Fraga's message of "Thu, 14 Jul 2022 07:01:55 +0000")

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

On 2022-07-14, Fraga, Eric wrote:

> On Thursday, 14 Jul 2022 at 08:13, Jens Lechtenboerger wrote:
>>   (list "index-terms"
> [...]
>>         :preparation-function 'oer-reveal--add-advice-link
>>         :completion-function 'oer-reveal--remove-advice-link
>>         :publishing-function '(org-html-publish-to-html)
>>         :publishing-directory "./public")
>> So, do you see theindex.org and theindex.inc?  Do you publish the
>> former?
> Yes, I do see theindex.org and theindex.inc but there are no index
> entries.

That is strange.  File theindex.inc should contain the index entries.
I believe that “:makeindex t” on the Org source files with #+INDEX:
entries should do the job.

> What do the first two functions listed above do?

They adapt the link format for my specific export backend (to point
to slides of presentations).  That is not relevant in your case.

Best wishes

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6187 bytes --]

  reply	other threads:[~2022-07-14  7:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 14:28 index for HTML export Fraga, Eric
2022-07-13 14:47 ` Fraga, Eric
2022-07-13 15:58   ` Fraga, Eric
2022-07-13 16:05     ` Fraga, Eric
2022-07-14  6:13       ` Jens Lechtenboerger
2022-07-14  7:01         ` Fraga, Eric
2022-07-14  7:18           ` Jens Lechtenboerger [this message]
2022-07-14  8:02             ` Fraga, Eric
2022-07-13 22:35 ` 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:

  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=87bkts5fio.fsf@wi.uni-muenster.de \
    --to=lechten@wi.uni-muenster.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).