From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf@spammotel.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Re: latex export settings in init files
Date: Mon, 28 Mar 2011 11:09:24 -0400 [thread overview]
Message-ID: <31255.1301324964@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from =?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf@spammotel.com> of "Mon\, 28 Mar 2011 15\:53\:10 +0200." <8039m7jqrd.fsf@somewhere.org>
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> 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?)
>
It depends on the comfort level of the user with org vs LaTeX as
well. If s/he wants to touch LaTeX as little as possible, Eric's
solution (combined with an #+INCLUDE file perhaps) is quite general and
it is perhaps more versatile: adding a class to org-export-latex-classes
buries it in some emacs initialization file; IMO, that's harder to
change (and find when you need to change it)[fn:1] but it may be the
appropriate way to deal with a more rigid LaTeX class setup that you
*always* (for some value of "always") want to follow.
BTW, does #+INCLUDE incorporate a path mechanism? That would go some
way into making this choice a "really doesn't matter which way you
go".
Nick
Footnotes:
[fn:1] But I freely admit that my emacs init setup is rather baroque,
thereby making things like that more difficult than they really need to
be. I also am somewhat allergic to customize (particularly when the spec
is complicated - as it is for org-export-latex-classes: I go cross-eyed
when I look at the customize screen for it), so I tend to avoid it in
most situations.
next prev parent reply other threads:[~2011-03-28 15:09 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
2011-03-28 15:09 ` Nick Dokos [this message]
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=31255.1301324964@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).