From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: "# <<tag>>" should stick to the following text
Date: Mon, 07 May 2012 09:10:25 +0200 [thread overview]
Message-ID: <87y5p44gbi.fsf@gmail.com> (raw)
In-Reply-To: <86wr4orffa.fsf@mercure.progiciels-bpi.ca> ("François Pinard"'s message of "Sun, 06 May 2012 20:41:13 -0400")
Hello,
François Pinard <pinard@iro.umontreal.ca> writes:
> When some feature is being deprecated, the Org manual should tell us,
> then ! :-) And at least where that feature is documented. Currently,
> the manual says:
>
> The preferred match for a text link is a dedicated target: the same
> string in double angular brackets.
This is correct. I was just pointing out (though, admittedly, not very
clearly) that the final part of the next sentence in the manual,
"sometimes it is convenient to put them into a comment line", isn't.
As I announced a few times already, targets are going to change a bit
and _commented_ targets will not be possible anymore in the new
exporter.
On the other hand, every regular target will be invisible. Let me
explain.
At the moment, "<<tag>>" and "# <<tag>>" produce, respectively, "<a
name="tag" id="tag">tag</a>" and "<a name="tag" id="tag"></a>".
In a not so distant future "<<tag>>" will produce "<a name="tag"
id="tag"></a>" and "# <<tag>>" will be ignored.
> I'll adapt of course, but to what? If not "# <<tag>>", then what is
> the way to create a named anchor at an arbitrary place in an Org file?
<<tag>> should suffice for that task.
I hope this is clearer now.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-05-07 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 20:35 "# <<tag>>" should stick to the following text François Pinard
2012-05-06 21:18 ` Nicolas Goaziou
2012-05-07 0:41 ` François Pinard
2012-05-07 1:44 ` François Pinard
2012-05-07 7:10 ` Nicolas Goaziou [this message]
2012-05-07 8:24 ` Eric S Fraga
2012-05-07 16:52 ` François Pinard
2012-05-08 14:14 ` Nick Dokos
2012-05-07 1:08 ` Nick Dokos
2012-05-07 5:14 ` Eric S Fraga
2012-05-08 8:33 ` Bastien
2012-05-07 5:34 ` Christian Moe
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=87y5p44gbi.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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).