From: Bastien <bzg@gnu.org>
To: Marco Falconi <marco.falconi@uniroma3.it>
Cc: emacs-orgmode@gnu.org
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:28:41 +0200 [thread overview]
Message-ID: <87d0305xgm.fsf@gnu.org> (raw)
In-Reply-To: <87lfjd6kmk.fsf@uniroma3.it> (Marco Falconi's message of "Tue, 21 Jul 2020 15:52:19 +0200")
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,
--
Bastien
next prev parent reply other threads:[~2020-09-05 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 13:52 Bug: Exporting internal link to special latex block [9.3.7 (9.3.7-14-gb2b587-elpa @ /home/lobo/.emacs.d/elpa/org-20200720/)] Marco Falconi
2020-08-04 6:41 ` Eric S Fraga
2021-04-18 15:42 ` Nicolas Goaziou
2020-09-05 10:28 ` Bastien [this message]
2020-09-05 10:56 ` Marco Falconi
2020-09-05 13:07 ` Bastien
2020-09-08 8:21 ` Nicolas Goaziou
2020-09-09 8:24 ` Bastien
2020-09-09 8:37 ` Bastien
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=87d0305xgm.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=marco.falconi@uniroma3.it \
/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).