From: Robert Goldman <rpgoldman@sift.info>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Making an index in latex export --- surprisingly difficult
Date: Tue, 26 Apr 2011 16:09:22 -0500 [thread overview]
Message-ID: <4DB73482.5010608@sift.info> (raw)
I was trying to make an index in latex export and found that it was very
difficult to make it work. I wonder if this could be simplified.
Here's what I had to do:
1. put \makeindex and \usepackage{makeidx} in latex export header [no
big deal]
2. put in \index commands (I don't /believe/ #+INDEX works, but I could
be wrong)
3. Put a \printindex in the end. [again, no big deal]
4. Modify the org-latex-to-pdf-process to
("pdflatex -interaction nonstopmode -output-directory %o %f" "makeindex
-o %b.ind %b.idx" "pdflatex -interaction nonstopmode -output-directory
%o %f" "pdflatex -interaction nonstopmode -output-directory %o %f")
[This was /somewhat/ of a big deal. Suggest we add support for indexing
as a built-in option, like bibtex...]
5. The REAL big deal: edit my texmf.cf file to break the security
protection of openout_any=p. By default, makeindex will refuse to open
an absolute pathname. But org-mode will only pass absolute pathnames to
makeindex (AFAICT). Question: it seems like bibtex should suffer from
this same restriction. Has anyone had that problem with it?
Cheers,
r
next reply other threads:[~2011-04-26 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:09 Robert Goldman [this message]
2011-04-26 21:26 ` Making an index in latex export --- surprisingly difficult Suvayu Ali
2011-04-26 21:44 ` Robert Goldman
2011-04-28 9:28 ` Eric S Fraga
2011-04-28 11:04 ` Robert Goldman
2011-04-28 11:52 ` Eric S Fraga
2011-04-26 21:52 ` Nick Dokos
2011-04-26 21:58 ` Robert Goldman
2011-04-26 23:14 ` Nick Dokos
2011-04-27 1:32 ` Robert Goldman
2011-04-27 6:35 ` Nick Dokos
2011-04-27 7:38 ` Thomas S. Dye
2011-05-09 6:08 ` Tom Dye
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=4DB73482.5010608@sift.info \
--to=rpgoldman@sift.info \
--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 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.