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:58:24 +0200 [thread overview]
Message-ID: <CAFgFV9MwZDYjNibAH+-EBMfBpNAu6KxjjkCX62PwX_Y4aU34Cg@mail.gmail.com> (raw)
In-Reply-To: <87h9luzgyd.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
2015-10-13 21:50 GMT+02:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> Fabrice Popineau <fabrice.popineau@gmail.com> writes:
>
> > 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:
>
> If I try to export this file, I get an error:
>
> user-error: Unable to resolve link: "foo"
>
> which is to be expected since :CUSTOM_ID: foo doesn't exist.
>
> > because if you use CUSTOM_ID in the first frame, the link is not
> > resolved.
>
> It should be. With the following document
>
> * Frame 1
> :PROPERTIES:
> :CUSTOM_ID: foo
> :END:
>
> * Frame 2
> :PROPERTIES:
> :BEAMER_env: againframe
> :BEAMER_ref: #foo
> :END:
>
> I get
>
> \begin{document}
>
> \begin{frame}[label={sec:orgheadline1}]{Frame 1}
> \end{frame}
>
> \againframe{{sec:orgheadline1}}
> \end{document}
>
> So, I'm still puzzled.
This time , I'm the one who is puzzled:
what is the point in naming the link "foo" and getting sec:orgheadline1
instead? :-)
If you add :BEAMER_OPT: label=foo
to the properties of the first frame, then you get the foo label.
But that doesn't seem very obvious to me. Why not taking directly the
CUSTOM_ID label ?
Fabrice
[-- Attachment #2: Type: text/html, Size: 2431 bytes --]
next prev parent reply other threads:[~2015-10-13 19:58 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
2015-10-13 19:50 ` Nicolas Goaziou
2015-10-13 19:58 ` Fabrice Popineau [this message]
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
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=CAFgFV9MwZDYjNibAH+-EBMfBpNAu6KxjjkCX62PwX_Y4aU34Cg@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 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).