From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Beffara Subject: Re: New exporter, beamer confusion Date: Thu, 7 Feb 2013 15:49:19 +0100 Message-ID: <48826909C0A84E91B223EF0A33E7D721@gmail.com> References: <20130204063905.GA23614@kuru.dyndns-at-home.com> <87wqun5037.fsf@gmail.com> <6207.1360048864@alphaville> <87fw1ashw5.fsf@gmail.com> <878v728fo0.fsf@ucl.ac.uk> <87ip65mfv5.fsf@gmail.com> <87mwvhkqye.fsf@ucl.ac.uk> <8738x8mhkg.fsf@gmail.com> <37646106030B4CA98C6A7717FBD89D50@gmail.com> <87vca4jigj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54121) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3StZ-0007lj-S9 for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 09:56:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U3StT-0007q9-PA for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 09:56:13 -0500 Received: from mail-we0-x22e.google.com ([2a00:1450:400c:c03::22e]:52822) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3StT-0007pw-G5 for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 09:56:07 -0500 Received: by mail-we0-f174.google.com with SMTP id r6so2142765wey.33 for ; Thu, 07 Feb 2013 06:56:05 -0800 (PST) In-Reply-To: <87vca4jigj.fsf@gmail.com> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Org Mode List Hi, > LaTeX class is never unspecified because `beamer' back-end is > a derivative of `latex', and, as such, `org-latex-default-class' will be > used. `beamer' could specify its own default class, but that class would > still need to be defined in `org-latex-classes'. Sure, it should be in the default list. What is the drawback? > '("beamer" > "\\documentclass[presentation]{beamer} > \[DEFAULT-PACKAGES] > \[PACKAGES] > \[EXTRA]" > ("\\section{%s}" . "\\section*{%s}") > ("\\subsection{%s}" . "\\subsection*{%s}") > ("\\subsubsection{%s}" . "\\subsubsection*{%s}")) Looks reasonable. > > Plain latex export is more problematic because several options are > > reasonable, but I can't see beamer export with an article class ... > > But it exists, and is documented in the Beamer User Guide. See section > "21.2. Creating Handouts Using the Article Mode". Yes, I know that, but the thing is, from a given org-file, I would expect beamer export to make the slides and 'plain' latex export to create the handout. Maybe it is difficult to achieve but it feels like the most useable setup. Is it at all doable? /v