From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Fabrice Popineau <fabrice.popineau@supelec.fr>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: BIND and LaTeX export
Date: Thu, 16 May 2013 19:52:24 +0200 [thread overview]
Message-ID: <871u96q0br.fsf@gmail.com> (raw)
In-Reply-To: <CAFgFV9MdufKWPZftT3ifxapdO5okQYET025Tk8rhmqYeNbPZyA@mail.gmail.com> (Fabrice Popineau's message of "Mon, 13 May 2013 21:13:50 +0200")
Hello,
Fabrice Popineau <fabrice.popineau@supelec.fr> writes:
> 2013/5/13 Nicolas Goaziou <n.goaziou@gmail.com>
>> Fabrice Popineau <fabrice.popineau@supelec.fr> writes:
>>
>> I'm surprised it even worked. BIND keywords only affect the export
>> process, i.e. Org to LaTeX translation in this case. File compilation to
>> PDF is a post-processing thing, these keywords don't survive that long.
>>
>>
> I may have been fooled by my emacs config.
> But anyway, given the name org-latex-*,
> I thought that it could make sense that this variable survive
> till the end of the compilation :-)
I understand the problem, but given the separation between the export
framework and its back-ends, it's difficult to do so.
Indeed, variables are bound in the temporary buffer copy created for the
translation but back-ends commands are only given a string (or a buffer
or a file name) containing the output. At this time, the copy isn't
alive anymore.
IOW, there are a few variables that cannot be set using BIND keywords.
On the other hand, they still can be set with file local variables.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2013-05-16 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 13:58 BIND and LaTeX export Fabrice Popineau
2013-05-13 17:07 ` Nicolas Goaziou
2013-05-13 19:13 ` Fabrice Popineau
2013-05-16 17:52 ` Nicolas Goaziou [this message]
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=871u96q0br.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fabrice.popineau@supelec.fr \
/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).