From: Zhihao Ding <zhihao.ding@imm.ox.ac.uk>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: latex options
Date: Mon, 30 Mar 2015 10:56:33 +0000 [thread overview]
Message-ID: <fa4ccea0-63d4-4f3d-99d0-89e9c71b02ed@HUB01.ad.oak.ox.ac.uk> (raw)
In-Reply-To: <olu619iydvd.fsf@med.uni-goettingen.de>
Thanks Andreas! This is very helpful.
I am using tags to control how verbose I want my export to be
and currently they differ slightly between projects. Quite often
I also have project specific tags. But no problem I think that’s
manageable with the layout you suggested.
Best,
Zhihao
> On 30 Mar 2015, at 11:32, Andreas Leha <andreas.leha@med.uni-goettingen.de> wrote:
>
> Hi Zhihao,
>
> Zhihao Ding <zhihao.ding@imm.ox.ac.uk> writes:
>> Dear Org experts,
>>
>> I was wondering if anyone could advise on this simple problem.
>> My toy org file, shown as below, contains 3 projects. I’d like to
>> export beamer PDFs for individual projects from time to time,
>> but the pain is that I always need to modify the header options
>> (title, select_tags etc) to match the project that I want to export.
>>
>> The question is what the best way is to organise the options for
>> multiple projects? Ideally I’d like to put a copy of the options
>> under each project, so that I only need to define them once.
>> It’d be even better if I could specify the file that I want the project
>> to be exported to instead of the same pdf file matching my org
>> file.
>>
>> #+TITLE: mytitle
>> #+AUTHOR: myself
>>
>> #+DATE: \today
>> #+LaTeX_CLASS: mybeamer
>>
>> #+SELECT_TAGS: export
>> #+EXCLUDE_TAGS: noexport
>>
>> #+OPTIONS: H:4 toc:nil *:
>>
>> ** project 1
>> ** project 2
>> ** project 3
>>
>
> You can add most of these keywords to the properties of a subtree by
> prepending them with 'export_'. I am not sure about the select tags,
> though. Why do you need them to differ between the projects?
>
>
> Your Example:
>
>
> --8<---------------cut here---------------start------------->8---
> #+TITLE: mytitle
> #+AUTHOR: myself
>
> #+DATE: \today
> #+LaTeX_CLASS: mybeamer
>
> #+SELECT_TAGS: export
> #+EXCLUDE_TAGS: noexport
>
> #+OPTIONS: H:4 toc:nil *:
>
> ** project 1
> :PROPERTIES:
> :header-args:R: :session *mysession1*
> :header-args: :cache yes
> :EXPORT_TITLE: mytitle 1
> :EXPORT_LaTeX_HEADER: \subtitle{mysubtitle 1}
> :EXPORT_FILE_NAME: myfile1
> :EXPORT_DATE: mydate 1
> :EXPORT_LaTeX_CLASS: mybeamer 1
> :EXPORT_OPTIONS: H:2 toc:nil
> :END:
> ** project 2
> :PROPERTIES:
> :header-args:R: :session *mysession2*
> :header-args: :cache yes
> :EXPORT_TITLE: mytitle 2
> :EXPORT_LaTeX_HEADER: \subtitle{mysubtitle 2}
> :EXPORT_FILE_NAME: myfile2
> :EXPORT_DATE: mydate 2
> :EXPORT_LaTeX_CLASS: mybeamer 2
> :EXPORT_OPTIONS: H:2 toc:nil
> :END:
> ** project 3
> :PROPERTIES:
> :header-args:R: :session *mysession3*
> :header-args: :cache yes
> :EXPORT_TITLE: mytitle 3
> :EXPORT_LaTeX_HEADER: \subtitle{mysubtitle 3}
> :EXPORT_FILE_NAME: myfile3
> :EXPORT_DATE: mydate 3
> :EXPORT_LaTeX_CLASS: mybeamer 3
> :EXPORT_OPTIONS: H:2 toc:nil
> :END:
> --8<---------------cut here---------------end--------------->8---
>
>
> HTH,
> Andreas
prev parent reply other threads:[~2015-03-30 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 9:28 latex options Zhihao Ding
2015-03-30 10:32 ` Andreas Leha
2015-03-30 10:56 ` Zhihao Ding [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=fa4ccea0-63d4-4f3d-99d0-89e9c71b02ed@HUB01.ad.oak.ox.ac.uk \
--to=zhihao.ding@imm.ox.ac.uk \
--cc=andreas.leha@med.uni-goettingen.de \
--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).