emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins < jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Wrong type argument: arrayp, nil when exporting to beamer [8.2 (8.2-elpa <at> /Users/jason/.emacs.d/elpa/org-20130919/)]
Date: Mon, 23 Sep 2013 00:54:03 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130923T024328-556@post.gmane.org> (raw)
In-Reply-To: 523F741E.4020005@dickson.st

Jason Lewis <jason <at> dickson.st> writes:

> Nicolas Goaziou wrote, On 23/09/2013 7:56 AM:
> > The syntax is wrong: you cannot have two frames within the same
> > tree.
> 
> Hi Nocolas,
> 
> Thanks. The error message is not very clear and this is an easy
> mistake for a beginner to make.

FWIW, I've been using the new beamer exporter for at least half a year, and 
I'm convinced the simplest way to handle frames is to set the H: export option 
to the heading level that you want to turn into frames. That is, typically I 
use top-level headings for sections, and my slideshows haven't been long 
enough yet to need subsections, so I set H:2 in one of the #+OPTIONS strings 
at the top. Then all "** Second level headings" become frames. No need to 
specify the beamer_env in the properties drawer.

It isn't always the case, but it does seem often to be true that simpler input 
avoids problems.

Hope that helps.

hjh

  reply	other threads:[~2013-09-23  0:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22  4:14 Bug: Wrong type argument: arrayp, nil when exporting to beamer [8.2 (8.2-elpa @ /Users/jason/.emacs.d/elpa/org-20130919/)] Jason Lewis
2013-09-22  4:41 ` Jason Lewis
2013-09-22 21:56   ` Nicolas Goaziou
2013-09-22 22:50     ` Jason Lewis
2013-09-23  0:54       ` James Harkins [this message]
2013-09-23 10:15       ` Nicolas Goaziou
     [not found]         ` <52457A6F.7050006@dickson.st>
2013-09-29  8:35           ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20130923T024328-556@post.gmane.org \
    --to=jamshark70@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).