From: Julien Cubizolles <j.cubizolles@free.fr>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: noninteractive use of org-export
Date: Thu, 17 Apr 2014 11:33:31 +0200 [thread overview]
Message-ID: <87tx9sxpuc.fsf@free.fr> (raw)
In-Reply-To: <877g6o8kvu.fsf@bzg.ath.cx> (Bastien's message of "Thu, 17 Apr 2014 09:39:49 +0200")
Bastien <bzg@gnu.org> writes:
> Hi Julien,
>
> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> How can I use org-beamer-export-to-pdf for example for an org file that
>> the current buffer isn't visiting?
>>
>> My setup is the following : I have two org files cours-beamer.org and
>> cours-notes.org each containing different +LATEX_CLASS and
>> +LATEX_CLASS_OPTIONS choices and the same +#INCLUDE "cours.org"
>> file. I'd like to be able to run the export to beamer-pdf for both
>> cours-beamer.org and cours-notes.org from cours.org, or even from a bash
>> script but the documentation for org-beamer-export-to-pdf doesn't show
>> how.
>
> You need to setup a publishing project to export several files at
> once.
Thanks that seems to be exactly what I need. However, I'm not sure I'm
doing everything right:
Here is what I've tried so far
(setq org-publish-project-alist
'(("cours"
:base-directory "~/tmp/test_org"
:publishing-directory "~/tmp/test_org"
:publishing-function org-beamer-publish-to-pdf
:include ("1er-principe-beamer.org" "1er-principe-notes.org"))))
Something must be wrong with the :include syntax since every org file in
the base-directory is exported when I run C-c C-e P x.
Also, is it possible to specify export options like LATEX_CLASS_OPTIONS
from org-publish-project-alist ?
Julien.
next prev parent reply other threads:[~2014-04-17 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 14:14 noninteractive use of org-export Julien Cubizolles
2014-04-16 15:06 ` Thorsten Jolitz
2014-04-17 7:39 ` Bastien
2014-04-17 9:33 ` Julien Cubizolles [this message]
2014-04-17 9:44 ` Bastien
2014-04-17 10:19 ` Julien Cubizolles
2014-04-17 10:38 ` Bastien
2014-04-17 13:09 ` Julien Cubizolles
2014-04-17 13:40 ` Bastien
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=87tx9sxpuc.fsf@free.fr \
--to=j.cubizolles@free.fr \
--cc=bzg@gnu.org \
--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).