From: Rasmus <rasmus@gmx.us>
To: e.fraga@ucl.ac.uk
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] [exporter] Frame labels cause allowframebreaks option to fail
Date: Tue, 15 Oct 2013 19:21:42 +0200 [thread overview]
Message-ID: <87ppr630wp.fsf@pank.iue.private> (raw)
In-Reply-To: <87y55ueee0.fsf@pinto.chemeng.ucl.ac.uk> (Eric S. Fraga's message of "Tue, 15 Oct 2013 16:35:03 +0100")
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
(I couldn't find any references to this problem, but I didn't look
very hard)
> The "label=sec-1-1-1" seems to make beamer ignore the allowframebreaks
> option. If I remove the label= directive from the options, everything
> works fine. Otherwise, the frame contents to not break over multiple
> frames.
> The question is: how can I tell the exporter to *not* generate label=
> directives? I have no need for these and, at the moment, I am having to
> edit the LaTeX source to get my slides done.
From a quick skim through ox-beamer I don't think you can disable it.
I don't know that it generally makes sense to do this.
You could use a regexp filter. Perhaps
org-export-filter-headline-functions like this quick-and-dirty
solution.
* test
:PROPERTIES:
:BEAMER_opt: allowframebreaks
:END:
hest
#+begin_src emacs-lisp
(defun rasmus/condtionally-remove-label (headline backend info)
"condtionally remove label"
(if (and
(org-export-derived-backend-p backend 'beamer)
(string-match "[.*?allowframebreaks.*?]" headline))
(replace-regexp-in-string ",? ?label=[-sec0-9]+" "" headline)
headline))
(add-to-list 'org-export-filter-headline-functions
'rasmus/condtionally-remove-label)
#+end_src
--
El Rey ha muerto. ¡Larga vida al Rey!
next prev parent reply other threads:[~2013-10-15 17:21 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 [this message]
2013-10-15 17:49 ` Rasmus
2013-10-16 7:15 ` Eric S Fraga
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=87ppr630wp.fsf@pank.iue.private \
--to=rasmus@gmx.us \
--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).