From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Problem with beamer export Date: Sun, 6 Oct 2013 20:36:32 -0500 Message-ID: References: <3630654D-6D57-484B-B9D6-5C0D5400BA17@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55769) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VSzkT-0001EO-0r for emacs-orgmode@gnu.org; Sun, 06 Oct 2013 21:36:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VSzkQ-00075B-Lj for emacs-orgmode@gnu.org; Sun, 06 Oct 2013 21:36:36 -0400 Received: from mail-la0-x229.google.com ([2a00:1450:4010:c03::229]:54468) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VSzkQ-000753-DG for emacs-orgmode@gnu.org; Sun, 06 Oct 2013 21:36:34 -0400 Received: by mail-la0-f41.google.com with SMTP id ec20so4971385lab.14 for ; Sun, 06 Oct 2013 18:36:33 -0700 (PDT) In-Reply-To: <3630654D-6D57-484B-B9D6-5C0D5400BA17@gmail.com> 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: Marvin Doyley Cc: "emacs-orgmode@gnu.org" On Sun, Oct 6, 2013 at 8:31 PM, Marvin Doyley wrote: > Hi John, > > This is an interesting bug. When I use the stable version of org i.e. 8.2.1 everything works as expected. > > To use xelatex I included the following in my .emacs file (some code I picked up several years ago > (setq org-latex-pdf-process (list > "xelatex -shell-escape -interaction nonstopmode -output-directory %o %f" > "xelatex -shell-escape -interaction nonstopmode -output-directory %o %f" > )) ;; for multiple passes > Based on my process, is it sufficient to have not reproduced your commands? Or can I just use the command you typed above to give it another whirl from the raw .tex file? On that note: - Is this an issue of converting Org syntax -> .tex syntax? OR... - Is this an issue of the .tex file -> xelatex -> .pdf? Re-thinking about your issue, it seems it's the former. In other words, if the .tex file doesn't have \frame, that's something wrong with Org -> .tex, not to do with the engine, right? If so, I'd probably look at diagnosing your Beamer definition, but I don't know how to. > With regards to the split beamer theme this is included in beamer. I am using texlive 2013 on the mac. > Sorry... I was unclear. I'm aware of the various themes. What I *didn't* understand is why your output said it was *using* the split them. Annnnddd... scrolled back up and just now caught that you included your beamer_header file that you included, which indeed says to use the split theme. Sorry about that! John > thanks > M > > On Oct 6, 2013, at 9:23 PM, John Hendy wrote: > >> On Sun, Oct 6, 2013 at 7:45 PM, Marvin Doyley wrote: >>> For more clarification >>> Here is a simple test file >> >> [snip] >> >> I can't current reproduce. I don't use xelatex, so I did `tlmgr >> install xetex` and the same for `xetex-def`. I wasn't sure if Org >> would pick up to use xelatex or not, so I took your example, exported >> to PDF via `C-c C-e l P` (for LaTeX Beamer) and then opened a terminal >> and did `xelatex test.tex`, the file Org created from my test.org file >> containing your contents. >> >> I attached the result. >> >> Some observations: >> - I noticed your latex output has beamer using the split theme. Where >> is it picking that? >> - You have a line in your #+ headers: `#+BEAMER_HEADER: >> \input{header_beamer} \date{}`. I don't have that file so I'm not sure >> what it does. I just removed it. >> - Here is my .emacs Beamer setting (default from the Org 8.0 new >> Beamer Worg page): >> >> #+begin_src .emacs >> >> (add-to-list 'org-latex-classes >> '("beamer" >> "\\documentclass\[presentation\]\{beamer\}" >> ("\\section\{%s\}" . "\\section*\{%s\}") >> ("\\subsection\{%s\}" . "\\subsection*\{%s\}") >> ("\\subsubsection\{%s\}" . "\\subsubsection*\{%s\}"))) >> >> #+end_src >> >> Again, see if the attached looks reasonable. Feel free to tell me how >> to more properly export via xelatex if you want someone to try and >> reproduce. I'm just not familiar with it at all, so I wasn't really >> sure bit gave it the 'ole college try. >> >> >> John >> >