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: Mon, 30 Dec 2013 18:16:05 +0100 [thread overview]
Message-ID: <CAGRH7Hri6zxo1yPT-rZ0yE-62HjLZ6nWV8QeDm5VhwnxmGrSbg@mail.gmail.com> (raw)
In-Reply-To: <CAGRH7HoQjDSX35L9caPmTA5PXje6Z45nXNdh8wCOpq6sDog3Sg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
Correction: CUSTOM_ID does not seem to work with description lists (it
seems it only works with headings, *, **, ***, ...).
Sébastien
2013/12/30 Sébastien Brisard <sebastien.brisard@m4x.org>
> Hi,
> thanks for your answer. This indeed works. Is was sure I had already
> tested this solution, with no success... Thanks a lot!!!
>
> Sébastien
>
>
> 2013/12/30 Nicolas Goaziou <n.goaziou@gmail.com>
>
>> Hello,
>>
>> Sébastien Brisard <sebastien.brisard@m4x.org> writes:
>>
>> > 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?
>>
>> You may use a custom-id syntax pointing to your target:
>>
>> [[file:./file2.org::#item-target][...]]
>>
>> Though, you will not get item number if you do not provide
>> a description.
>>
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>
>
[-- Attachment #2: Type: text/html, Size: 1818 bytes --]
next prev parent reply other threads:[~2013-12-30 17:16 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 [this message]
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=CAGRH7Hri6zxo1yPT-rZ0yE-62HjLZ6nWV8QeDm5VhwnxmGrSbg@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).