From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Specify org-latex-pdf-process for a single file?
Date: Mon, 20 Jul 2015 21:19:04 +0530 [thread overview]
Message-ID: <77E5F0AB-D72D-40BA-AB97-D8EE6A34000C@agrarianresearch.org> (raw)
In-Reply-To: <878uabdsvb.fsf@ucl.ac.uk>
Thanks all. I was not familiar with this way of defining local variables. Just checked the relevant part of the manual. Very useful.
Thanks,
Vikas
> On 20-Jul-2015, at 3:59 pm, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
> On Monday, 20 Jul 2015 at 07:05, Vikas Rawal wrote:
>> How do I specify org-latex-pdf-process for a single file? I am working
>> on a book manuscript, where I need to run makeindex and biber, along
>> with xelatex. That is not normally needed in every document. Can I
>> org-latex-pdf-process in the document itself?
>>
>> Vikas
>
> I have the following at the end of most of my org files that are
> intended to be exported to LaTeX et al.:
>
> --8<---------------cut here---------------start------------->8---
> # Local Variables:
> # org-export-allow-bind-keywords: t
> # org-latex-pdf-process: ("pdflatex %f")
> # eval: (esf/execute-startup-block)
> # End:
> --8<---------------cut here---------------end--------------->8---
>
> where the src block esf/execute-startup-block does more general file
> specific settings. Obviously, adapt the pdf process variable to your
> needs.
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1260-gcedef7
next prev parent reply other threads:[~2015-07-20 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 1:35 Specify org-latex-pdf-process for a single file? Vikas Rawal
2015-07-20 2:15 ` Thomas S. Dye
2015-07-20 9:13 ` Rasmus
2015-07-20 10:29 ` Eric S Fraga
2015-07-20 15:49 ` Vikas Rawal [this message]
2015-07-27 8:42 ` Sebastien Vauban
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=77E5F0AB-D72D-40BA-AB97-D8EE6A34000C@agrarianresearch.org \
--to=vikaslists@agrarianresearch.org \
--cc=e.fraga@ucl.ac.uk \
--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).