Hello, François Pinard <pin...@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
