Re: Re: IMPORTANT: (possibly) incompatible Change

[Mark Elston <m_elston@comcast.net>]

Carsten,

Is there a way to *remove* one or more of the packages in
org-export-latex-default-packages-alist?  I find that marvosym
is conflicting with one of the packages I use in my notes and
handouts that I generate from org-mode.  (marvosym and bbding
both provide a Cross - I don't use that symbol but it interferes
with latex processing to have them both defined)

I suppose a way to remove one or more packages in *specific*
export classes would be ideal...

Mark

On 4/2/2010 12:55 AM, Carsten Dominik wrote:
>
> On Apr 2, 2010, at 3:17 AM, Mark Elston wrote:
>
>> Carsten,
>>
>> Thanks for this clarification. This makes the transition much
>> simpler than I originally thought. I can certainly remove the
>> common package names.
>>
>> The existing org-export-latex-classes also contains the
>> documentclass line. That won't change, will it? I am
>> assuming from what you have written that the generated LaTeX code
>> will be something like:
>>
>> <contents of org-export-latex-classes for the selected class>
>> <contents of org-export-latex-default-packages-alist>
>> <contents of org-export-latex-packages-alist for the selected class>
>
> Yes. But the latter two variables are independent of class.
> And after these three components, #+LaTeX_HEADER stuff will be
> added as well.
>
> - Carsten
>
>>
>> Is this correct?
>>
>> Mark
>>
>> On 3/31/2010 11:59 PM, 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