From: Eric Schulte <schulte.eric@gmail.com>
To: Ista Zahn <izahn@psych.rochester.edu>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Portability
Date: Mon, 04 Jul 2011 14:54:14 -0600 [thread overview]
Message-ID: <87aactkbf4.fsf@gmail.com> (raw)
In-Reply-To: CA+vqiLGq1DBKK8jDe+xVkS7Dk1TGc8zehhbTd0RxQOzFYq5dew@mail.gmail.com
Ista Zahn <izahn@psych.rochester.edu> writes:
> Hi all,
> Over the past couple of days I've been happily tweaking my org-mode
> settings. At one point something happened that gave me great pause. I
> forgot to load a function that adds an APA style LaTeX export (using
> apa6e.cls) to my org-export-latex-classes Alist. So of course when I
> tried to export using that class it did not work. This made me realize
> that my .org document depended on my .emacs file for export! This
> strikes me as a very bad thing because if I want others to be able to
> use my .org document I have to distribute (at least the relevant parts
> of) my .emacs along with it.
>
> So all this got me thinking that perhaps setting up lots of
> complicated org-mode related stuff in my .emacs is a bad idea, and
> that perhaps I should use a template to do the setup in each .org
> file.
>
> Please share any tips or suggestions you have related to this. What do
> you do? How well does it work? What suggestions do you have for
> someone just starting out with org-mode?
>
> Thanks!
>
I find that file-local-variables can be a convenient and portable way to
include the relevant Org-mode configuration in the actual org-mode file
itself. See [1], specifically the second longer form which can be
placed at the end of a file. I've used this to specify custom latex
classes, as well as change default export options.
Best -- Eric
Footnotes:
[1] http://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html
--
Eric Schulte
http://cs.unm.edu/~eschulte/
prev parent reply other threads:[~2011-07-04 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 19:16 Portability Ista Zahn
2011-07-04 20:54 ` Eric Schulte [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=87aactkbf4.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=izahn@psych.rochester.edu \
/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).