From: Stephen Jeffrey Barr <stevejb@uw.edu>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: Using allowframebreaks in org-beamer
Date: Tue, 12 Nov 2013 15:35:48 -0800 [thread overview]
Message-ID: <87zjp9b3cb.fsf@uw.edu> (raw)
In-Reply-To: <87li0tx5sg.fsf@pinto.chemeng.ucl.ac.uk>
Thank you for the clarification Eric. That did exactly what I wanted it to!
Best,
Stephen
e.fraga@ucl.ac.uk writes:
> "Stephen J. Barr" <stevejb@uw.edu> writes:
>
>> I agree with the "less stuff" part. The first pass in my slides is for
>> content, second pass is for formatting :-). For now, I did manual division
>> of the sides. I am using both org-beamer and org-reveal (
>> https://github.com/yjwen/org-reveal) and ideally they would have optimized
>> (and possibly different) slide breaks. E.g. perhaps beamer breaks 9
>> elements into 3 3-elements slides whereas reveal breaks into 2 slides, one
>> with 5 elements and one of 4 elements.
>>
>> I'll look around for the previous post but in the mean time I think I will
>> stick with method 0.
>
> To summarise the previous post (i.e. from the thread I started for this
> bug), all you have to do is simply include the following on any slide
> for which you want frame breaks:
>
> --8<---------------cut here---------------start------------->8---
> * A long "frame" with breaks
> :PROPERTIES:
> :BEAMER_opt: allowframebreaks,label=
> :END:
> --8<---------------cut here---------------end--------------->8---
>
> Method 0 is, in principle, desirable, but I actually find that beamer
> does a really nice job on automatic frame breaks in most cases and it
> makes writing some types of presentations much easier! An example, from
> my own usage, is the solution to some example problem when teaching. I
> can simply write down all the steps, e.g. as an enumerated list, and let
> beamer worry about the breaks. Using automatic frame breaks, for me, is
> just the obvious extension of org (or LaTeX): let me worry about the
> content and let the system worry about the formatting!
>
> From LyX: "what you see is what you mean" :-)
prev parent reply other threads:[~2013-11-12 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 21:34 Using allowframebreaks in org-beamer Stephen J. Barr
2013-11-12 2:13 ` Rasmus
2013-11-12 3:22 ` Stephen J. Barr
2013-11-12 10:39 ` Eric S Fraga
2013-11-12 23:35 ` Stephen Jeffrey Barr [this message]
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=87zjp9b3cb.fsf@uw.edu \
--to=stevejb@uw.edu \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).