emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] ox-beamer and CUSTOM_ID


From: Fabrice Popineau
Subject: Re: [O] ox-beamer and CUSTOM_ID
Date: Tue, 13 Oct 2015 21:58:24 +0200



2015-10-13 21:50 GMT+02:00 Nicolas Goaziou <address@hidden>:
Fabrice Popineau <address@hidden> writes:

> 2015-10-13 21:26 GMT+02:00 Nicolas Goaziou <address@hidden>:
>
>> 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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]