From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Fabrice Popineau <fabrice.popineau@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: ox-beamer and CUSTOM_ID
Date: Tue, 13 Oct 2015 21:38:48 +0200 [thread overview]
Message-ID: <CAFgFV9Nhta9VvPLU0L=nfww7Jh5nfQU178sMkWqrQVoNTKfXHA@mail.gmail.com> (raw)
In-Reply-To: <87pp0izi1f.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
2015-10-13 21:26 GMT+02:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> Hello,
>
> I don't understand the issue. BEAMER_REF: #foo generates the same
> internal reference as :CUSTOM_ID: foo, doesn't it?
>
>
My point is that you need to set :
* Frame 1
:PROPERTIES:
:BEAMER_OPT: label=foo
:END:
* Frame 2
:PROPERTIES:
:BEAMER_env: againframe
:BEAMER_ref: #foo
:END:
because if you use CUSTOM_ID in the first frame, the link is not resolved.
The code at stake is :
ox-beamer:org-beamer-headline which calls ox-beamer:org-beamer--get-label
at line 624
Clearly, org-beamer--get-label doesn't make use of CUSTOM_ID.
It is a bit strange to have to use another way to set custom labels than a
CUSTOM_ID property.
Regards,
Fabrice
[-- Attachment #2: Type: text/html, Size: 1434 bytes --]
next prev parent reply other threads:[~2015-10-13 19:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 11:24 ox-beamer and CUSTOM_ID Fabrice Popineau
2015-10-13 19:26 ` Nicolas Goaziou
2015-10-13 19:38 ` Fabrice Popineau [this message]
2015-10-13 19:50 ` Nicolas Goaziou
2015-10-13 19:58 ` Fabrice Popineau
2015-10-13 20:52 ` Nicolas Goaziou
2015-10-13 21:12 ` Fabrice Popineau
2015-10-13 22:18 ` Nicolas Goaziou
2015-10-14 9:47 ` Fabrice Popineau
2015-10-14 11:57 ` Nicolas Goaziou
2015-10-14 12:18 ` Fabrice Popineau
2015-10-15 8:37 ` Nicolas Goaziou
2015-10-15 16:54 ` Fabrice Popineau
2015-10-15 19:25 ` Fabrice Popineau
2015-10-15 19:48 ` Nicolas Goaziou
2015-10-15 20:20 ` Fabrice Popineau
2015-10-16 20:59 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFgFV9Nhta9VvPLU0L=nfww7Jh5nfQU178sMkWqrQVoNTKfXHA@mail.gmail.com' \
--to=fabrice.popineau@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.