From: Jan Ulrich Hasecke <juh@mailbox.org>
To: Org-Mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Indexing with org-mode
Date: Sun, 30 Jul 2023 13:00:54 +0200 [thread overview]
Message-ID: <ZMZC5k614gA3k+mn@odysseus> (raw)
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Hi all,
for some years I am using the Python documentation tool Sphinx to write
manuals. My target formats are epub and pdf. Sphinx has a very
comfortable and powerful indexing mechanism which makes indexing very
easy.
In the last weeks I went back to an older Sphinx project, which I now
want to finish. As I am now mostly using org-mode for my writing I
evaluated if it was feasible to convert the Sphinx project to org-mode.
But as I found no good solution for indexing in org-mode I didn't
converted it to org-mode.
I found two mentions about indexing in the manual: Texinfo indexing and
indexing in publishing via :makeindex. Both don't work in my exports.
I am using GNU Emacs 28.2 with straight using the newest packages.
I am exporting either with ox-context or org-pandoc to ConTeXt.
I managed to use Texinfo indexing in ox-context some months ago, but now
it doesn't work anymore. Maybe I forgot the configuration or an upgrade
broke it. I remember that I had to use a feature-branch to make it work
at all.
For some time now ox-context seems to be completely broken for me as it
does not export the main text. The consequence is that I work with
org-pandoc to create context pdfs from my org-mode files.
So I have a couple of problems with org-mode and context, but the main
problem is indexing.
Does anyone know of a new approach to indexing in org-mode?
TIA
juh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-07-30 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 11:00 Jan Ulrich Hasecke [this message]
2023-07-30 11:49 ` Indexing with org-mode Ihor Radchenko
2023-07-30 12:21 ` juh
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=ZMZC5k614gA3k+mn@odysseus \
--to=juh@mailbox.org \
--cc=emacs-orgmode@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 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).