From: Robert Goldman <rpgoldman@sift.info>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Latex export to documentclass beamer
Date: Mon, 17 Aug 2009 09:43:47 -0500 [thread overview]
Message-ID: <4A896CA3.6050003@sift.info> (raw)
This seems like a very common thing to want to do, but am I right in
thinking that it's also very hard to get right because the frame
environment is not really a sectioning environment?
As I understand things, the way we export to latex is to insert
sectioning commands, and drop translated content in between.
However, this doesn't seem like the right model for Beamer.
Consider a crude talk outline like this:
* Here's a simple point
Some material here
* Here's a complex point
** First component point
Explanation
** Second component point
More explanation....
The "right" way to translate this is something like
\section{Here's a simple point}
\begin{frame}
\frametitle{Here's a simple point}
...
\end{frame}
\section{Here's a complex point}
\begin{frame}
\frametitle{First component point}
....
\end{frame}
\begin{frame}
\frametitle{Second component point}
....
\end{frame}
------------------------------------------
I.e., there's some rule like "If a header has text under it, then treat
it as a frame, otherwise, just treat it as a section header."
You see this above, where the two top-level headers are treated differently.
I can't think of any obvious way to translate org to beamer that doesn't
require choosing a /specific/ level of the outline as "the level that
corresponds to a frame," and doing that seems to seriously compromise
the outlining flexibility of org-mode.
Am I missing something here? Is there some better way to figure out how
to introduce frames, instead of treating them as sectioning headers?
thanks,
R
next reply other threads:[~2009-08-17 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 14:43 Robert Goldman [this message]
2009-08-17 16:17 ` Latex export to documentclass beamer Robert Goldman
2009-08-17 18:19 ` Nick Dokos
2009-08-17 18:35 ` Robert Goldman
-- strict thread matches above, loose matches on Subject: below --
2009-08-09 13:05 RC
2009-08-09 14:17 ` Carsten Dominik
2009-08-09 15:45 ` RC
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A896CA3.6050003@sift.info \
--to=rpgoldman@sift.info \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.