From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jason Lewis <jason@dickson.st>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Wrong type argument: arrayp, nil when exporting to beamer [8.2 (8.2-elpa @ /Users/jason/.emacs.d/elpa/org-20130919/)]
Date: Mon, 23 Sep 2013 12:15:59 +0200 [thread overview]
Message-ID: <87k3i73ktc.fsf@gmail.com> (raw)
In-Reply-To: <523F741E.4020005@dickson.st> (Jason Lewis's message of "Mon, 23 Sep 2013 08:50:06 +1000")
Hello,
Jason Lewis <jason@dickson.st> writes:
> Thanks. The error message is not very clear and this is an easy
> mistake for a beginner to make.
I think that nesting frames is a strange error to make.
Anyway, here is the relevant part of the manual:
- Headlines become frames when their level is equal to
'org-beamer-frame-level' or 'H' value in an 'OPTIONS' line (*note
Export settings::).
Though, if a headline in the current tree has a 'BEAMER_ENV'
property set to either to 'frame' or 'fullframe', its level
overrides the variable. A 'fullframe' is a frame with an empty
(ignored) title.
Do you think it should be reformulated? If so, could you suggest what
would be needed?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-09-23 10:15 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 ` Bug: Wrong type argument: arrayp, nil when exporting to beamer [8.2 (8.2-elpa <at> /Users/jason/.emacs.d/elpa/org-20130919/)] James Harkins
2013-09-23 10:15 ` Nicolas Goaziou [this message]
[not found] ` <52457A6F.7050006@dickson.st>
2013-09-29 8:35 ` Bug: Wrong type argument: arrayp, nil when exporting to beamer [8.2 (8.2-elpa @ /Users/jason/.emacs.d/elpa/org-20130919/)] 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=87k3i73ktc.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jason@dickson.st \
/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).