From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Portable formatting of export?
Date: Tue, 22 Oct 2013 09:49:35 +0200 [thread overview]
Message-ID: <87li1l7njk.fsf@gmx.us> (raw)
In-Reply-To: CANtbJLGN57vPEV8==mgSrKhdcbbaToSeKG7+8ic-7cxuRs1Aow@mail.gmail.com
Hi Klaus,
Klaus-Dieter Bauer <bauer.klaus.dieter@gmail.com> writes:
> This left me wondering however, if it is possible to create org files that
> will produce the same output on every machine, regardless of the local
> emacs customizations (of course assuming that no hacks of the export engine
> are part of the configuration).
The authority on fully reproducible exports on this list is
Thomas S. Dye. You might be able to find his posts searching
for "Aloha". I believe he has a per-project .el file with settings.
You could also have settings in a Babel emacs-lisp block. I do that
sometimes. Then use e.g. org-babel-load-file.
> In order to make the files more portable I have been trying to make changes
> affecting export with things like #+LATEX_HEADER: but e.g. changing the
> documentclass to scrartcl seems to be possible only by changing a
> customization variable (org-latex-classes).
Customizatoins through org-latex-classes are a lot more comfortable
than adding all those LaTeX headers IMO.
> Is it possible to make the export engine assume defaults for all
> customization variables for a file (preferably through an in-file setting)
> and to specify those customization inside the file?
Yes.
And you can always check that it works as expected with emacs -q.
–Rasmus
--
May the Force be with you
prev parent reply other threads:[~2013-10-22 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 19:39 Portable formatting of export? Klaus-Dieter Bauer
2013-10-21 19:55 ` Eric Schulte
2013-10-22 15:05 ` Klaus-Dieter Bauer
2013-10-22 17:17 ` Thomas S. Dye
2013-10-22 7:49 ` Rasmus [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=87li1l7njk.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).