Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Eric S Fraga
Rasmus ras...@gmx.us writes: Eric S Fraga e.fr...@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:

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Eric S Fraga
Eric S Fraga e.fr...@ucl.ac.uk writes: Rasmus ras...@gmx.us writes: Eric S Fraga e.fr...@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

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Carsten Dominik
Hi Eric, I think ox-beamer will turn id: links, search links and custom-id lines into clickable references in beamer. I have not tried this myself, but looking at the code, this seems to be the case. Regards - Carsten On Oct 16, 2013, at 12:25 PM, Eric S Fraga e.fr...@ucl.ac.uk wrote:

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Rasmus
Eric writes: If not, it may be simplest to apply the patch I posted yesterday which removes the automatic generation of frame labels. Did you try the /second/ filter I posted? It should do what you want, but only break the frames that has the offending mark. Carsten Dominik

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Carsten Dominik
test, please ignore, may mailer is acting up. On Oct 16, 2013, at 12:25 PM, Eric S Fraga e.fr...@ucl.ac.uk wrote: Eric S Fraga e.fr...@ucl.ac.uk writes: Rasmus ras...@gmx.us writes: Eric S Fraga e.fr...@ucl.ac.uk writes: Hello, technically, I guess this is a bug in beamer and not in

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Andreas Leha
Rasmus ras...@gmx.us writes: Eric writes: If not, it may be simplest to apply the patch I posted yesterday which removes the automatic generation of frame labels. Did you try the /second/ filter I posted? It should do what you want, but only break the frames that has the offending mark.

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Eric S Fraga
Andreas Leha andreas.l...@med.uni-goettingen.de writes: [...] Hi all, I had the same problem and :BEAMER_opt: allowframebreaks,label= (with an empty label) does the trick for me here. Brilliant! This does work and doesn't require any filters or changes to org. Thanks. -- : Eric S

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Eric S Fraga
Carsten Dominik drostekirs...@gmail.com writes: Hi Eric, I think ox-beamer will turn id: links, search links and custom-id lines into clickable references in beamer. I have not tried this myself, but looking at the code, this seems to be the case. Indeed but I'm not sure what this has to

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-16 Thread Nicolas Goaziou
Hello, Eric S Fraga e.fr...@ucl.ac.uk writes: Carsten Dominik drostekirs...@gmail.com writes: Hi Eric, I think ox-beamer will turn id: links, search links and custom-id lines into clickable references in beamer. I have not tried this myself, but looking at the code, this seems to be the

[O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-15 Thread Eric S Fraga
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} The

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-15 Thread Eric S Fraga
Eric S Fraga e.fr...@ucl.ac.uk writes: [...] 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. I found some time to look at the code and it appears that

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-15 Thread Rasmus
Eric S Fraga e.fr...@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:

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-15 Thread Rasmus
Eric S Fraga e.fr...@ucl.ac.uk writes: A better solution would be to have a variable to be able to customise this behaviour, I imagine. Why? Labels are /usually/ completely harmless. Please open a bug report at Beamer's Bitbucket. –Rasmus -- I hear there's rumors on the, uh, Internets. .

Re: [O] [bug] [exporter] Frame labels cause allowframebreaks option to fail

2013-10-15 Thread Rasmus
Rasmus ras...@gmx.us writes: #+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))