emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: latex export settings in init files
Date: Mon, 28 Mar 2011 15:53:10 +0200	[thread overview]
Message-ID: <8039m7jqrd.fsf@somewhere.org> (raw)
In-Reply-To: 87ipv3lac1.fsf@ucl.ac.uk

Hi Eric,

Eric S Fraga wrote:
> By the way, for the types of customisation you are doing above (obviously, I
> don't know what you have omitted), I find it easier to define an org
> template that has the appropriate #+LaTeX_CLASS_OPTIONS and #+LATEX_HEADER
> lines.

I guess that you mean it "if the number of custom LaTeX lines is < 5 or 10",
something like that.

Even in such a case, I would opt the OP for his own document class (or style
file), so that every custom is only made once, in one place. And, would he
recompile his Org doc later, he would benefit from all the updated features he
put in his class -- if nothing is contradictorily changed...

Your argument is maybe about being "easier". True. And false: after all,
what's a class or style file, everything you want except for the first few
lines, and the last one, no?

(not trying to say the opposite of you ;-) but give the OP another "sound of
clock" -- maybe you think as well at other points I'm missing here?)

Best regards,
  Seb

-- 
Sébastien Vauban

  parent reply	other threads:[~2011-03-28 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 11:55 latex export settings in init files Chris Beard
2011-03-28 12:05 ` Eric S Fraga
2011-03-28 12:32   ` Chris Malone
2011-03-28 13:53   ` Sébastien Vauban [this message]
2011-03-28 15:09     ` Nick Dokos
2011-03-28 15:31     ` Eric S Fraga
2011-03-28 19:59 ` Aankhen

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=8039m7jqrd.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).