emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: BEAMER_FRAME_LEVEL + subtree export
Date: Sun, 26 Feb 2012 21:53:45 +0800	[thread overview]
Message-ID: <87linp3dli.wl%jamshark70@dewdrop-world.net> (raw)

Getting deeper into beamer export and enjoying it -- props to the responsible developers.

A point of fine print that escaped me in the available documentation -- maybe I just overlooked, but probably this is something that should be clarified.

When doing a buffer export, #+BEAMER_FRAME_LEVEL refers to the absolute subheading level: 2 == **, 3 = *** etc.

For a subtree export, you need to subtract the level of the subtree being exported.

#+BEAMER_FRAME_LEVEL: 2

#+TITLE:     Show #1
#+AUTHOR:    dlm
#+EMAIL:     dlm@dlm-laptop
#+DATE:      2012-02-26 Sun
* Presentation 1
** Section 1
*** Frame 1
    Some text
*** Frame 2
    More text

At first I thought I would need to set the frame level to 3 (because "*** Frame 1"), but it needs to be 2 for a subtree export originating from "Presentation 1" because the frames are two levels underneath the top level.

I can easily imagine that the frame level is documented as relative to the subtree being exported -- just pointing out that this is an easy place to get confused and probably would benefit from stating explicitly.

hjh


--
James Harkins /// dewdrop world
jamshark70@dewdrop-world.net
http://www.dewdrop-world.net

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal."  -- Whitman

blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks

                 reply	other threads:[~2012-02-26 13:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87linp3dli.wl%jamshark70@dewdrop-world.net \
    --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).