Aloha Carsten and others,

The Worg FAQ on beamer export describes a setup that isn't up-to-date:

http://orgmode.org/worg/org-faq.php#beamer

All the best,
Tom

On Apr 1, 2010, at 6:51 AM, Carsten Dominik wrote:

>
> On Apr 1, 2010, at 6:17 PM, Thomas S. Dye wrote:
>
>> Aloha Carsten,
>>
>> Packages that aren't used for all classes can still appear in org- 
>> export-latex-classes, correct?
>
> Aloha Tom,
>
> Anything can appear there.  But you should not have the packages I  
> have listed in the new variable org-export-latex-default-packages- 
> alist, because these will be used anyway.  If you keep them in org- 
> export-latex-classes, they will be called twice (which may or may  
> not be a problem....)
>
> - Carsten
>
>>
>> All the best,
>> Tom
>>
>> On Apr 1, 2010, at 1:13 AM, Carsten Dominik wrote:
>>
>>> 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
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
>