From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Farseer He <admin@farseer.cn>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: ox-publish(html) needs org-link-unescape while treating external search link [9.0.9 (9.0.9-68-g492420-elpaplus @ /home/farseer/.emacs.d/elpa/org-plus-contrib-20170807/)]
Date: Sat, 22 Sep 2018 23:33:55 +0200 [thread overview]
Message-ID: <878t3tdxoc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r2hoeec1.fsf@farseer-workstation.i-did-not-set--mail-host-address--so-tickle-me> (Farseer He's message of "Thu, 20 Sep 2018 16:57:18 +0800")
Hello,
Farseer He <admin@farseer.cn> writes:
> Problem: ox-publish (to html for example) generates incoherent external
> links for search links like [[file:foo%20bar.org::*h1][link example]].
> Suppose the h1 element in "foo bar.html" has ID "#orgffffff", the
> generated external html anchor link may refer to ID "#org000000".
>
> Probable reason: Different IDs get generated to org-publish-cache, 1 for
> h1 in "foo bar.org", the other (generated by org-resolve-external-link)
> for h1 in "foo%20bar.org". I suppose that "org-link-unescape" should be
> called before written to cache.
>
> Emacs : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
> of 2018-07-05
> Package: Org mode version 9.0.9 (9.0.9-68-g492420-elpaplus @
> /home/farseer/.emacs.d/elpa/org-plus-contrib-20170807/)
I think this was fixed in a more recent version. Could you verify it?
Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2018-09-23 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 8:57 Bug: ox-publish(html) needs org-link-unescape while treating external search link [9.0.9 (9.0.9-68-g492420-elpaplus @ /home/farseer/.emacs.d/elpa/org-plus-contrib-20170807/)] Farseer He
2018-09-22 21:33 ` Nicolas Goaziou [this message]
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=878t3tdxoc.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=admin@farseer.cn \
--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).