emacs-orgmode
[Top][All Lists]
Advanced

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

Re: Bug: Exporting internal link to special latex block [9.3.7 (9.3.7-14


From: Marco Falconi
Subject: Re: Bug: Exporting internal link to special latex block [9.3.7 (9.3.7-14-gb2b587-elpa @ /home/lobo/.emacs.d/elpa/org-20200720/)]
Date: Sat, 05 Sep 2020 12:56:41 +0200
User-agent: mu4e 1.3.9; emacs 27.1

Dear Bastien,

Thanks for the update. For the moment I have worked around the bug by putting an
html-export block in the org file with the correct href when I have to put a 
link to it.

However, it would be very nice if it was solved in org. Also, my preference 
would be for
the exported id to be the one given in the NAME attribute (as it is now), 
because I use it
in the html file to name the theorem environment. Of course this is just my 
preference,
and I would understand if the solution would work in another manner.

Best regards,
_____
Marco


Bastien <bzg@gnu.org> writes:

> Hi Marco,
>
> Marco Falconi <marco.falconi@uniroma3.it> writes:
>
>> I am trying to export to html a labeled latex special block (a theorem
>> environment, defined by #+begin_theorem [...] #+end_theorem ). I have named 
>> the theorem with
>>
>> #+NAME: thm:mv (I also tried with #+LABEL: and the behavior described below 
>> does not change).
>>
>> I have a link to such block later in the body, in the form [[thm:mv]]. The 
>> link works
>> perfectly in the org file, however it is exported incorrectly to html.
>>
>> In fact, while the theorem environment gets exported in the html as
>>
>>    <div class="theorem" id="thm:mv">
>>    <p>
>>    [...]
>>    </p>
>>    </div>
>>
>> ,
>>
>> the link does not href to "#thm:mv" as expected, but to an auto-generated 
>> label:
>>
>>     <p>
>>     <a href="#orgd9d024a">1</a>
>>     </p>
>>
>> I have tried to play around a bit with export options, but to no avail.
>>
>> Is this a known bug?
>
> I also confirm this bug.  I've had a quick look.  It looks like
> `org-export-get-reference' get fooled by trying to provide with a "new
> reference".  I hope Nicolas can have a look because this area of the
> code is quite complexe.
>
> Thanks,




reply via email to

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