From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [New exporter] Wrong export to LaTeX Date: Fri, 12 Oct 2012 14:09:02 +0200 Message-ID: <87hapz3na9.fsf@gmail.com> References: <80txu1ma6t.fsf@somewhere.org> <87bog9401p.fsf@gmail.com> <20121011165232.GB15182@kuru.dyndns-at-home.com> <877gqw51z9.fsf@gmail.com> <20121012102434.GA24769@kuru.dyndns-at-home.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36227) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TMe6l-0003oO-Lp for emacs-orgmode@gnu.org; Fri, 12 Oct 2012 08:12:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TMe6h-0003Lu-KK for emacs-orgmode@gnu.org; Fri, 12 Oct 2012 08:12:51 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:52819) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TMe6h-0003Lo-Bd for emacs-orgmode@gnu.org; Fri, 12 Oct 2012 08:12:47 -0400 Received: by mail-we0-f169.google.com with SMTP id u3so1880566wey.0 for ; Fri, 12 Oct 2012 05:12:46 -0700 (PDT) In-Reply-To: <20121012102434.GA24769@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Fri, 12 Oct 2012 12:24:34 +0200") 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: Suvayu Ali Cc: emacs-orgmode@gnu.org Hello, Suvayu Ali writes: > Okay, I do follow this. However, doesn't LaTeX_CLASS determine what > goes into the \documentclass{class name} directive? No. Key in `org-e-latex-class' is just a label. You can have an association like: ("foo" "\\documentclass{article}" ...) It is here to help you name different configurations. > If so, does having \begin{frames}..\end{frames} in the exported tex > make sense if the documentclass directive says, for example, article? You can use article, or book document classes along with Beamer, i.e. when you want to create handouts for your presentation. This requires to load "beamerarticle" package (cf. Beamer documentation). So, yes it can make sense to call Beamer back-end on an "article" documentclass. > What I'm getting at is, without the LaTeX_CLASS set to beamer, the > crucial \documentclass{beamer} directive is missing and the exported > LaTeX document won't be compilable[1]. Given the preceding comments are > correct, I would then say having a "beamer" class already defined in > org-e-beamer will save new users some trouble. Is my analysis valid, or > am I grossly wrong? Like in the LaTeX back-end, if you specify some class, you have to make sure it does match an association in `org-e-latex-classes'. Though, having a class named "beamer" isn't mandatory: you can have many classes named differently and all using internally "\\documentclass{beamer}". Also, I don't want to automatically modify a defcustom (`org-e-latex-classes') once `org-e-beamer' is loaded. It isn't very clean, even with careful checks. `e-beamer' could also default to some header when provided class doesn't match, but that looks ugly, too. > Footnotes: > > [1] I tried this with the LaTeX_CLASS set to article, and there were > errors in the exported pdf. Because, in that case, your header must contain: \usepackage{beamerarticle} Regards, -- Nicolas Goaziou