emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Brisard" <sebastien.brisard@m4x.org>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode-publish: link to dedicated target accross files
Date: Sun, 29 Dec 2013 20:17:44 +0100	[thread overview]
Message-ID: <CAGRH7HpdBdRR8VV=+50bLhW-Ld-=S7GEqB-fipbY+_7LvQ5MLA@mail.gmail.com> (raw)
In-Reply-To: <87ppofqyjg.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

Hi,
that's what I feared... I know it works with the CUSTOM_ID property.
Unfortunately, I'd like to link to an item in a list.
Is there a (possibly dirty) work around?

Best regards,
Sébastien


2013/12/29 Nicolas Goaziou <n.goaziou@gmail.com>

> Hello,
>
> Sébastien Brisard <sebastien.brisard@m4x.org> writes:
>
> > I'm facing a problem with links accross multiple org files, when I
> publish
> > to HTML. Here is a minimal working example. file1.org looks like
> >
> > <<target1>> Target 1
> >
> > [[target1][Go to target #1]]
> >
> > [[file:./file2.org::target2][Go to target #2]]
> >
> > while file2.org looks like
> >
> > <<target2>> Target 2
> >
> > In emacs, when I click on the second link, it opens file2.org all right.
> > However, when I export to html, here is what file1.html looks like
> >
> > <body>
> >   <div id="content">
> >     <h1 class="title">file1</h1>
> >     <p>
> >       <a id="target1" name="target1"></a> Target 1
> >     </p>
> >
> >     <p>
> >       <a href="#target1">Go to target #1</a>
> >     </p>
> >
> >     <p>
> >       <a href="./file2.html">Go to target #2</a>
> >     </p>
> >   </div>
> >   <div id="postamble" class="status">
> >     ...
> >   </div></body>
> >
> > The second link should read (I believe)
> >
> > <a href="./file2.html#target2">Go to target #2</a>
>
> There's no support for exporting links to targets across files. You can
> only target a headline, through its custom-id, e.g.,
>
>   [[file:./file2.org::#custom-id][...]]
>
> or through its title
>
>   [[file:/file2.org::*Headline title][...]]
>
>
> Regards,
>
> --
> Nicolas Goaziou
>

[-- Attachment #2: Type: text/html, Size: 2791 bytes --]

  reply	other threads:[~2013-12-29 19:17 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 [this message]
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
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='CAGRH7HpdBdRR8VV=+50bLhW-Ld-=S7GEqB-fipbY+_7LvQ5MLA@mail.gmail.com' \
    --to=sebastien.brisard@m4x.org \
    --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).