emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] [exporter] Frame labels cause allowframebreaks option to fail
Date: Wed, 16 Oct 2013 14:07:26 +0200	[thread overview]
Message-ID: <877gddctc1.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87bo2ph3j6.fsf@pank.eu

Rasmus <rasmus@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.
>
> Carsten Dominik <drostekirsten@gmail.com> writes:
>
>> 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.
>
> Correct, it seems.  Check this example
>
> * test  
> (require 'ox-beamer)
>
> * test 2 
>   [[test]]
>
>
> Of course custom-id is better.
>
> –Rasmus

Hi all,

I had the same problem and 
   :BEAMER_opt: allowframebreaks,label=
(with an empty label) does the trick for me here.

- Andreas

  reply	other threads:[~2013-10-16 12:07 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
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 [this message]
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=877gddctc1.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --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).