From: Marco Falconi <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com 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 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> 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 <firstname.lastname@example.org> writes: > Hi Marco, > > Marco Falconi <email@example.com> 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,
next prev parent reply other threads:[~2020-09-05 10:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-21 13:52 Marco Falconi 2020-08-04 6:41 ` Eric S Fraga 2021-04-18 15:42 ` Nicolas Goaziou 2020-09-05 10:28 ` Bastien 2020-09-05 10:56 ` Marco Falconi [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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/)]' \ /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
Code repositories for project(s) associated with this 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).