From: Robert Goldman <email@example.com>
To: Suvayu Ali <firstname.lastname@example.org>
Subject: Re: Making an index in latex export --- surprisingly difficult
Date: Tue, 26 Apr 2011 16:44:05 -0500 [thread overview]
Message-ID: <4DB73CA5.email@example.com> (raw)
On 4/26/11 Apr 26 -4:26 PM, Suvayu Ali wrote:
> On Tue, 26 Apr 2011 16:09:22 -0500
> Robert Goldman <firstname.lastname@example.org> wrote:
>> 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?
> I did and no clean solution has been found yet.
I looked at that thread and unfortunately it petered out (partly because
it went off into a different direction to solve an easier problem with
conflicting style files).
The last message from Eric Fraga states:
> Oh well, there goes that theory. The web link you gave yesterday would seem to indicate that the problem is present if you invoke the bibtex command from another directory and this does not appear to be the case here. Very strange.
It's not actually invoking the bibtex command from another directory,
AFAICT, but invoking the bibtex command on an argument that is an
/absolute/ pathname. This is now forbidden for makeindex and bibtex (I
don't know if it's permitted for pdflatex or not, but I suspect it is,
since the pdflatex part of the export process is working --- pdflatex
may not honor openout_any=p).
I don't see why, per the discussion in the texlive distribution notes,
it should matter that you change the TEXMF pathname environment
variable, since makeindex isn't doing any metafonting!
I also don't see any obvious way for programs like org-mode to adapt to
this except possibly by explicitly changing their working directory to
be the working directory of the org files and then using relative
pathnames instead of absolute ones. And I would like to say right now
that I don't have the FOGGIEST idea what that would mean on Windows,
which seems to think about working directories somewhat differently!
next prev parent reply other threads:[~2011-04-26 21:44 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 [this message]
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
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 \
* 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).