From: Carsten Dominik <dominik@uva.nl>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: IMPORTANT: (possibly) incompatible Change
Date: Thu, 1 Apr 2010 13:13:08 +0200 [thread overview]
Message-ID: <795F8D4A-D936-479B-AC14-66F1DB85E500@uva.nl> (raw)
In-Reply-To: <9667B267-935B-4DFB-800B-FC76DBCCBF28@gmail.com>
OK, this change is now in the master branch.
- Carsten
On Apr 1, 2010, at 8:59 AM, Carsten Dominik wrote:
> Hi Mark,
>
> OK, it seems that I have really overstated this change. You are of
> course right that your header for a document type can be very long,
> that that defining it in org-export-latex-classes is a viable option
> (other being to put this stuff into a separate file).
>
> So let me restate what I am trying to say in this thread.
>
> ------------------------------------------------------------------------------
> Org-mode contains now a new variable `org-export-latex-default-
> packages-alist'
> which contains all the LaTeX packages it needs to use for basic Org-
> mode
> functionality. The corresponding \usepackage statements used to be
> part
> of the header definitions in org-export-latex-classes, and they had to
> be repeated for each document class. This is wasteful, error prone,
> and
> hard to maintain.
> Therefore, these packages are now collected in the new variable,
> and they will be spliced into the header.
>
> If you have customized the variable org-export-latex-classes, you
> need to
> remove the following lines from each class definition:
>
> \usepackage[AUTO]{inputenc}
> \usepackage[T1]{fontenc}
> \usepackage{graphicx}
> \usepackage{longtable}
> \usepackage{float}
> \usepackage{wrapfig}
> \usepackage{soul}
> \usepackage{latexsym}
> \usepackage{amssymb}
> \usepackage{hyperref}
>
> If you have other packages you always want to use in all
> classes, you can add them to another variable,
> `org-export-latex-packages-alist'.
> ------------------------------------------------------------------------------
>
>
> I think this makes more sense, thank you for making me clarify this.
>
> - Carsten
>
>
>
> On Mar 31, 2010, at 8:41 PM, Mark Elston wrote:
>
>> On 3/31/2010 5:35 AM, Carsten Dominik wrote:
>>>
>>> On Mar 31, 2010, at 11:00 AM, Chris Gray wrote:
>>>
>>>> Carsten Dominik wrote:
>>>>
>>>>> -----------------------------------------------------------------------------
>>>>>
>>>>> * =org-export-latex-classes= no longer should be customized for
>>>>> packages
>>>> ...
>>>>> So if you have customized this variable, please remove once more
>>>>> (hopefully for the last time) your customization, so that it can
>>>>> revert to its now much simpler default value. Put all your
>>>>> package definitions into org-export-latex-packages-alist.
>>>>> I hope this works, and we will not get conflicts because of the
>>>>> sequence in which packages are called. If there are problems,
>>>>> please let me know so that we can find a solution.
>>>>
>>>> Is it sufficient to change the variable that is being set from
>>>> org-export-latex-classes to org-export-latex-default-packages-
>>>> alist? Or
>>>> does the format of the list change at all?
>>>
>>> org-export-latex-default-packages-alist has the same format as
>>> org-export-latex-pakcages-alist. And I am filling
>>> org-export-latex-default-packages-alist already with the correct
>>> set of
>>> default packages, so you should not touch that variable.
>>>
>>> Only if you have previously customized org-export-latex-classes in
>>> order
>>> to add more usepackage statements, then you should remove your
>>> customization of that variable and list your set of additional
>>> packages
>>> in org-export-latex-packages-alist instead.
>>>
>>> Am I making sense?
>>>
>>
>> So, org-export-latex-classes will no longer be used to define
>> LaTeX_CLASS classes? Instead these classes will be defined in
>> org-export-latex-default-packages-alist?
>>
>> The problem is mainly nomenclature, I guess, but my LaTeX_CLASS
>> definitions are usually a *lot* more than a list of packages.
>>
>> It seems a little odd, but OK.
>>
>> Mark
>>
>>
>> _______________________________________________
>> 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
>
>
>
- Carsten
next prev parent reply other threads:[~2010-04-01 11:13 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 [this message]
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
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
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=795F8D4A-D936-479B-AC14-66F1DB85E500@uva.nl \
--to=dominik@uva.nl \
--cc=carsten.dominik@gmail.com \
--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).