From: Carsten Dominik <carsten.dominik@gmail.com>
To: Karsten Heymann <karsten.heymann@blue-cable.net>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: IMPORTANT: (possibly) incompatible Change
Date: Tue, 6 Apr 2010 16:53:04 +0200 [thread overview]
Message-ID: <7C341FD3-C6E5-4555-9FC2-90E31B40E94C@gmail.com> (raw)
In-Reply-To: <87d3ycg5e1.fsf@ara.blue-cable.net>
On Apr 6, 2010, at 1:57 PM, Karsten Heymann wrote:
> Hi,
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>> On Apr 4, 2010, at 12:50 AM, Henri-Paul Indiogine wrote:
>>> When I export to LaTeX the line \definecolor..... comes before
>>> \usepackage{color} then it throws an error during compilation.
>>> If I
>>> move the \definecolor... _after_ \usepackage{color} it compiles.
>>>
>>> Is are a way to setup my LaTeX export so that this happens
>>> automagically?
>>
>> No, I think you need to return to the old way of configuring
>> everything in org-export-latex-classes.
>
> Suggestion: Would it be hard to add a location marker for the place
> the
> default packages are included? Something like
>
> (setq org-export-latex-classes
> '(("book"
> "\\documentclass[11pt]{book}
> (include-org-standard-packages-here)
> \\definecolor{darkblue}{rgb}{0.0,0.0,0.3}
> \\hypersetup{colorlinks,breaklinks,
>
> If (include-org-standard-packages-here) is missing, the \usepackage
> lines are appended to the template. This way one could use the
> standard
> packages and at the same time use commands from the packages in the
> preamble.
Great idea, so I am proud that I came up with it already. This is
just like it works in 6.35, only with different place holders.
- Carsten
>
> Yours
> Karsten
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-04-06 14:53 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 22:24 IMPORTANT: (possibly) incompatible Change Carsten Dominik
2010-03-31 9:00 ` Chris Gray
2010-03-31 12:35 ` Carsten Dominik
2010-03-31 14:16 ` Eric Schulte
2010-03-31 14:18 ` Carsten Dominik
2010-03-31 18:41 ` Mark Elston
2010-04-01 6:59 ` Carsten Dominik
2010-04-01 11:13 ` Carsten Dominik
2010-04-01 16:17 ` Thomas S. Dye
2010-04-01 16:51 ` Carsten Dominik
2010-04-02 16:25 ` Thomas S. Dye
2010-04-02 1:17 ` Mark Elston
2010-04-02 7:55 ` Carsten Dominik
2010-04-03 18:49 ` Mark Elston
2010-04-03 22:50 ` Henri-Paul Indiogine
2010-04-03 22:55 ` Carsten Dominik
[not found] ` <87pr2gezp9.fsf@belvoir.org>
[not found] ` <A3285E87-A435-4CD9-B5BF-13330A09CE63@gmail.com>
2010-04-04 17:36 ` Henri-Paul Indiogine
2010-04-04 19:44 ` Mark Elston
2010-04-06 11:57 ` Karsten Heymann
2010-04-06 14:53 ` Carsten Dominik [this message]
2010-04-03 22:57 ` Carsten Dominik
2010-04-03 23:25 ` Mark Elston
2010-04-04 0:14 ` Carsten Dominik
2010-04-04 5:47 ` Nick Dokos
2010-04-04 6:39 ` Carsten Dominik
2010-04-06 12:30 ` Karsten Heymann
2010-04-06 14:53 ` Carsten Dominik
2010-04-06 16:03 ` Karsten Heymann
2010-04-06 16:23 ` Carsten Dominik
2010-04-06 16:50 ` Karsten Heymann
2010-04-06 18:30 ` Robert Klein
2010-04-06 18:48 ` Thomas S. Dye
2010-04-07 7:37 ` Carsten Dominik
2010-04-07 8:22 ` Karsten Heymann
2010-04-07 8:47 ` Carsten Dominik
2010-04-07 10:31 ` Karsten Heymann
2010-04-07 15:51 ` Thomas S. Dye
2010-04-07 16:00 ` Carsten Dominik
2010-04-10 17:30 ` Mark Elston
2010-04-10 20:01 ` Thomas S. Dye
2010-04-11 3:40 ` Mark Elston
2010-04-07 8:16 ` Karsten Heymann
2010-04-07 7:38 ` Carsten Dominik
2010-04-07 9:15 ` Ulf Stegemann
2010-04-07 10:30 ` Karsten Heymann
2010-04-07 11:58 ` Ulf Stegemann
2010-04-07 12:24 ` Karsten Heymann
2010-04-02 1:29 ` [PATCH] " Eric Schulte
2010-04-02 2:47 ` Mark Elston
2010-04-02 5:38 ` Carsten Dominik
2010-04-03 16:20 ` Henri-Paul Indiogine
2010-04-03 16:55 ` Carsten Dominik
2010-04-03 17:19 ` Xiao-Yong Jin
2010-04-06 10:25 ` Carsten Dominik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7C341FD3-C6E5-4555-9FC2-90E31B40E94C@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=karsten.heymann@blue-cable.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.