From: John Tait <johngtait@gmail.com>
To: emacs-orgmode@gnu.org, e.fraga@ucl.ac.uk
Subject: Re: LaTeX beamer class text
Date: Thu, 5 May 2011 12:57:10 +0100 [thread overview]
Message-ID: <BANLkTikKCKVL8yoOPRg8Ckuh94Kb8S7-iQ@mail.gmail.com> (raw)
In-Reply-To: <87oc3h4md6.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
Thanks for your reply. I think a global option would be useful because I
mightn't know in advance whether I'd need slides for particular headings or
not. I'm thinking of a use case where I have produced a long LaTeX article
and have selected certain tags to do so, and I would build a beamer
presentation to brief it out by adding a :briefing: tag to a subset of the
exported article headings (so the beamer slides are more concise).
John
On Thu, May 5, 2011 at 8:50 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> John Tait <johngtait@gmail.com> writes:
>
> > Matt (and Daniel Bausch -- sorry for double post earlier)
> >
> > I've found that beamer "allowframebreaks" doesn't work for Org files that
> > have been included with #+INCLUDE: .
>
> [...]
>
> > Is there a way to "allowframebreaks" work globally or at least in
> included
> > files?
>
> I've gone through the beamer manual but haven't seen any way of doing
> so. However, it was a cursory look so maybe you could check it out more
> closely (the manual is >200 pages long...).
>
> I wouldn't recommend allowframebreaks as a global option, in any case.
> IMO, that leads to sloppy slide design, but this *is* my opinion only!
> There are times where it is needed but it is generally better to be
> conscious of needing it. Just my two ¢...
>
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
> : using Org-mode version 7.5 (release_7.5.249.gbf7ce.dirty)
>
[-- Attachment #2: Type: text/html, Size: 1977 bytes --]
prev parent reply other threads:[~2011-05-05 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 12:36 LaTeX beamer class text John Tait
2011-04-27 16:20 ` Matt Lundin
2011-04-28 22:49 ` John Tait
2011-05-03 11:21 ` John Tait
2011-05-05 7:50 ` Eric S Fraga
2011-05-05 11:57 ` John Tait [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=BANLkTikKCKVL8yoOPRg8Ckuh94Kb8S7-iQ@mail.gmail.com \
--to=johngtait@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).