From: Fabrice Popineau <fabrice.popineau@supelec.fr>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: BIND and LaTeX export
Date: Mon, 13 May 2013 21:13:50 +0200 [thread overview]
Message-ID: <CAFgFV9MdufKWPZftT3ifxapdO5okQYET025Tk8rhmqYeNbPZyA@mail.gmail.com> (raw)
In-Reply-To: <8761ymu7tk.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
2013/5/13 Nicolas Goaziou <n.goaziou@gmail.com>
> Hello,
>
> Fabrice Popineau <fabrice.popineau@supelec.fr> writes:
>
> > Is it me or something is wrong with the very latest org-mode (git
> > repository).
> > I have this line in my org-file :
> >
> > #+BIND: org-latex-pdf-process ("pdflatex -interaction nonstopmode
> > -shell-escape -output-directory %o %f")
> >
> > My default value for this variable states that lualatex is used for
> > compilation.
> > Even using the BIND line, it is still lualatex which is used.
> > And I have set org-export-allow-bind-keywords to t.
> >
> > I'm pretty sure it worked a couple of days ago.
>
> 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 :-)
> You may use file local variables instead.
>
>
Thanks for the hint.
Fabrice
[-- Attachment #2: Type: text/html, Size: 1938 bytes --]
next prev parent reply other threads:[~2013-05-13 19:14 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 [this message]
2013-05-16 17:52 ` Nicolas Goaziou
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=CAFgFV9MdufKWPZftT3ifxapdO5okQYET025Tk8rhmqYeNbPZyA@mail.gmail.com \
--to=fabrice.popineau@supelec.fr \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).