From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Fabrice Niessen <fni-news@pirilampo.org>, emacs-orgmode@gnu.org
Subject: Re: Better way to specify the latex documentclass of an exported file without changing my configuration?
Date: Wed, 26 Mar 2014 23:03:58 +0100 [thread overview]
Message-ID: <m2bnwsy5v5.fsf@polytechnique.org> (raw)
In-Reply-To: <m2zjkc23yd.fsf@tsdye.com> (Thomas S. Dye's message of "Wed, 26 Mar 2014 08:46:18 -1000")
Hello Tom,
tsd@tsdye.com (Thomas S. Dye) writes:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> I usually export in offline mode, so I can keep editing while the export
>> is going on.
>
> If you and your colleagues export asynchronously, then the document
> class (and other environment changes) can be placed in an initialization
> file for the asynchronous process.
>
> An approach that I'm exploring tangles this initialization file from
> code that is kept in a noexport section of the document. See
> http://orgmode.org/worg/exporters/plos-one-template-worg.html for an
> example that likely can be improved.
This would clearly make our export process more robust and reproducible.
Thanks a lot for the link, I'll look into it.
Alan
next prev parent reply other threads:[~2014-03-26 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 8:37 Better way to specify the latex documentclass of an exported file without changing my configuration? Alan Schmitt
2014-03-26 9:24 ` Feng Shu
2014-03-26 12:38 ` Fabrice Niessen
2014-03-26 12:53 ` Alan Schmitt
2014-03-26 18:46 ` Thomas S. Dye
2014-03-26 22:03 ` Alan Schmitt [this message]
2014-03-26 12:47 ` Alan Schmitt
2014-03-26 23:26 ` Richard Lawrence
2014-03-26 13:21 ` Nicolas Goaziou
2014-03-26 13:54 ` Alan Schmitt
2014-03-26 14:10 ` Nicolas Goaziou
2014-03-26 14:57 ` Alan Schmitt
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=m2bnwsy5v5.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=fni-news@pirilampo.org \
--cc=tsd@tsdye.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).