From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Sébastien Brisard" <sebastien.brisard@m4x.org>
Cc: Rick Frankel <rick@rickster.com>, emacs-orgmode@gnu.org
Subject: Re: Org-mode-publish: link to dedicated target accross files
Date: Wed, 01 Jan 2014 19:13:20 +0100 [thread overview]
Message-ID: <878uuzefjz.fsf@gmail.com> (raw)
In-Reply-To: <CAGRH7HrSmJZvaJ1dUzzhkjuVF4ZyTLk4aMGo0u13TTrNGzGrPQ@mail.gmail.com> ("Sébastien Brisard"'s message of "Tue, 31 Dec 2013 18:44:40 +0100")
Hello,
Sébastien Brisard <sebastien.brisard@m4x.org> writes:
> If I instead write
>
> [[file:./references.org::HASH1962][Hashin and Shtrikman (1962)]]
>
> (without the #), then the behaviour is the exact opposite
> 3. in Emacs, the link (including the dedicated target) is found
> 4. in the exported HTML file, the link is incomplete (<a
> href="./references.html">...</a>)
>
> What I would like is 2 + 3...
I have pushed a change to html back-end (in master branch) so that an
unresolved option should still appear in the exported link. IOW,
[[file:./file.org::target][...]]
will become
<a href="./file.html#target">...</a>
This is slightly different from link resolution in a single buffer,
because, in the case above, a headline named "* target" will have
priority over a "<<target>>".
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-01-01 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 16:20 Org-mode-publish: link to dedicated target accross files Sébastien Brisard
2013-12-29 18:53 ` Nicolas Goaziou
2013-12-29 19:17 ` Sébastien Brisard
2013-12-30 9:43 ` Nicolas Goaziou
2013-12-30 17:00 ` Sébastien Brisard
2013-12-30 17:16 ` Sébastien Brisard
2013-12-30 19:46 ` Nicolas Goaziou
2013-12-30 20:28 ` Sébastien Brisard
2013-12-30 22:05 ` Nicolas Goaziou
2013-12-31 17:44 ` Sébastien Brisard
2014-01-01 18:13 ` Nicolas Goaziou [this message]
2014-01-03 13:51 ` Sébastien Brisard
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=878uuzefjz.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rick@rickster.com \
--cc=sebastien.brisard@m4x.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).