From: Jambunathan K <kjambunathan@gmail.com>
To: Matt Lundin <mdl@imapmail.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: COMMENTed Radio Targets: Any comments?
Date: Sat, 06 Nov 2010 12:28:26 +0530 [thread overview]
Message-ID: <81wrorndkd.fsf@gmail.com> (raw)
In-Reply-To: <87y697h563.fsf@fastmail.fm> (Matt Lundin's message of "Fri, 05 Nov 2010 16:44:04 -0400")
Hello Matt
> For stable links to particular headlines, I would recommend CUSTOM_IDs
> over radio targets. E.g.,
I am raising these questions or bugs or even aberrations as a result of
my work on OpenOffice.
IOW, I am not looking at 'using them as a feature' but to 'understand
them as a feature' and 'cross-checking' my OpenOffice's exporter against
the HTML exporter.
So the question of swithching to custom-ids doesn't arise in my case.
Jambunathan K.
Matt Lundin <mdl@imapmail.org> writes:
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> I am noticing Some inconsistencies with commented out 'Radioed
>> Targets'. Example is down below. Comments are welcome ...
>>
>> In the generated HTML,
>>
>> 1. The section titled 'Radioed Target' is not exported because it is
>> commented out.
>> 2. References to 'Radioed Target' still get exported as link. It
>> points to self.
>>
>> I am not sure what the right behaviour should be ...
>
> AFAIK, there are no tests in the exporter to determine whether the
> target of such a link actually exists.
>
>> * Links
>> ** Targets
>> *** COMMENT <<<Radioed Target>>>
>> ** References
>> *** References to Radioed Links
>> This section has references to Radioed Target.
>
> For stable links to particular headlines, I would recommend CUSTOM_IDs
> over radio targets. E.g.,
>
> * Links
> ** Targets
> :PROPERTIES:
> :CUSTOM_ID: target
> :END:
> ** References
> *** References to Radioed Links
> This section has references to Radioed Target.
>
> Best,
> Matt
next prev parent reply other threads:[~2010-11-06 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 14:09 COMMENTed Radio Targets: Any comments? Jambunathan K
2010-11-05 20:44 ` Matt Lundin
2010-11-06 6:58 ` Jambunathan K [this message]
2010-11-06 14:24 ` Matt Lundin
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=81wrorndkd.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).