From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] [exporter] Frame labels cause allowframebreaks option to fail
Date: Wed, 16 Oct 2013 08:15:02 +0100 [thread overview]
Message-ID: <87ppr56615.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87ppr630wp.fsf@pank.iue.private> (rasmus@gmx.us's message of "Tue, 15 Oct 2013 19:21:42 +0200")
Rasmus <rasmus@gmx.us> writes:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> Hello,
>>
>> technically, I guess this is a bug in beamer and not in org's
>> exporter. However, if I specify the =allowframebreaks= option for a
>> frame, the exporter generates the following LaTeX code on beamer export:
>>
>> \begin{frame}[allowframebreaks,label=sec-1-1-1]{Some definitions}
>
> Interesting (I can reproduce here). Perhaps you should fill a bug
> report:
>
> https://bitbucket.org/rivanvx/beamer/wiki/Home
Thanks for the confirmation. I will file a report. It is indeed a
problem with beamer and not org but, for the time being, I have modified
org (my copy) to avoid the problem as I need to generate my slides for
lectures now...
Also thanks for the other suggestions on how to filter the export.
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.2.1-84-g2829fd
next prev parent reply other threads:[~2013-10-16 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 15:35 [bug] [exporter] Frame labels cause allowframebreaks option to fail Eric S Fraga
2013-10-15 16:51 ` Eric S Fraga
2013-10-15 17:24 ` Rasmus
2013-10-15 17:21 ` Rasmus
2013-10-15 17:49 ` Rasmus
2013-10-16 7:15 ` Eric S Fraga [this message]
2013-10-16 10:25 ` Eric S Fraga
2013-10-16 11:04 ` Carsten Dominik
2013-10-16 11:13 ` Rasmus
2013-10-16 12:07 ` Andreas Leha
2013-10-16 13:08 ` Eric S Fraga
2013-10-16 13:13 ` Eric S Fraga
2013-10-16 19:14 ` Nicolas Goaziou
2013-10-16 11:47 ` Carsten Dominik
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=87ppr56615.fsf@ucl.ac.uk \
--to=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).