From: Nick Dokos <nicholas.dokos@hp.com>
To: rpgoldman@sift.info
Cc: nicholas.dokos@hp.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Making an index in latex export --- surprisingly difficult
Date: Tue, 26 Apr 2011 19:14:01 -0400 [thread overview]
Message-ID: <6699.1303859641@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Robert Goldman <rpgoldman@sift.info> of "Tue, 26 Apr 2011 16:58:41 CDT." <4DB74011.2020600@sift.info>
Robert Goldman <rpgoldman@sift.info> wrote:
> >> 2. put in \index commands (I don't /believe/ #+INDEX works, but I could
> >> be wrong)
>
> Am I right about #+INDEX not being translated in the latex back end (it
> seems not to work, but it's hard to verify a negative)?
>
Seems to be a publishing thingie only. Adding a publishing project
--8<---------------cut here---------------start------------->8---
...
("foo"
:base-directory "~/src/org/latex/index/"
:publishing-directory "~/src/org/latex/index"
:publishing-function org-publish-org-to-latex
:makeindex t
)
...
--8<---------------cut here---------------end--------------->8---
to org-publish-project-alist and publishing the following org file
--8<---------------cut here---------------start------------->8---
#+INDEX: foo
* this
is a test of foo
--8<---------------cut here---------------end--------------->8---
generates \index{foo} in the TeX file.
Nick
> If so, would this be hard to fix? If it wouldn't, seems like that would
> be A Good Thing.
>
next prev parent reply other threads:[~2011-04-26 23:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:09 Making an index in latex export --- surprisingly difficult Robert Goldman
2011-04-26 21:26 ` 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 [this message]
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
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=6699.1303859641@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=rpgoldman@sift.info \
/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).