From: Nicolas Goaziou <n.goaziou@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [new exporter] is #+bind supported?
Date: Wed, 06 Mar 2013 11:21:38 +0100 [thread overview]
Message-ID: <877glk25hp.fsf@gmail.com> (raw)
In-Reply-To: <87r4jsykpx.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 6 Mar 2013 08:51:38 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
> [...]
>
>> Bind keywords are supported. Unfortunately, `org-latex-pdf-process' is
>> not bind-able.
>>
>> BIND variables are set as buffer-local variables in the buffer where the
>> transcoding takes place. So, they affect the way the current buffer is
>> changed into LaTeX code.
>>
>> However, `org-latex-pdf-process' is used during post-processing, i.e.
>> after transcoding is over. At this time, the buffer where local
>> variables were set has disappeared already.
>
> Okay, I see how this works. Thanks for the explanation. Would it not
> be possible to set the bound variables for the latex buffer as well? Or
> does that open up a can of worms? Just curious.
There is no latex buffer. Export produces a string. Whet it is complete,
the current buffer is the original buffer from which the original
command was issued.
IOW, what you suggest means that BIND keywords should set local
variables in the original buffer. I'm not sure it is the intended goal
for these keywords.
If you need to set a local buffer variable, it is better to use the
dedicated tools.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2013-03-06 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 14:20 [new exporter] is #+bind supported? Eric S Fraga
2013-03-05 14:33 ` Achim Gratz
2013-03-05 16:52 ` Eric S Fraga
2013-03-05 18:18 ` Achim Gratz
2013-03-06 8:44 ` Eric S Fraga
2013-03-06 20:09 ` Achim Gratz
2013-03-07 8:36 ` Eric S Fraga
2013-03-05 22:07 ` Nicolas Goaziou
2013-03-06 8:51 ` Eric S Fraga
2013-03-06 10:21 ` 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=877glk25hp.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--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).