emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Carsten Dominik <drostekirsten@gmail.com>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: [bug] [exporter] Frame labels cause allowframebreaks option to fail
Date: Wed, 16 Oct 2013 21:14:06 +0200	[thread overview]
Message-ID: <87k3hdm3k1.fsf@gmail.com> (raw)
In-Reply-To: <8761sxqryc.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 16 Oct 2013 14:13:31 +0100")

Hello,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Carsten Dominik <drostekirsten@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 do with automatic generation of
> labels of the form sec-1-1-1?  I understand the benefit of user
> specified links, whichever way they are created.  I just don't see the
> use case for automatic labelling.  Or am I missing something really
> fundamental here?  (with org, that is often the case as I think I maybe
> understand <5% of what it is capable of...)

If you don't label frames, internal links are broken, unless there's
a way to refer to a frame without labelling it first.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-10-16 19:14 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
2013-10-16 13:08             ` Eric S Fraga
2013-10-16 13:13         ` Eric S Fraga
2013-10-16 19:14           ` Nicolas Goaziou [this message]
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=87k3hdm3k1.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=drostekirsten@gmail.com \
    --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).