From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: "# <>" should stick to the following text Date: Tue, 08 May 2012 10:14:56 -0400 Message-ID: <12032.1336486496@alphaville> References: <8662c9rqtq.fsf@mercure.progiciels-bpi.ca> <87397dgg9a.fsf@gmail.com> <86wr4orffa.fsf@mercure.progiciels-bpi.ca> <87y5p44gbi.fsf@gmail.com> Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRlCF-0000cP-W0 for emacs-orgmode@gnu.org; Tue, 08 May 2012 10:15:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SRlC5-0000Hw-Uj for emacs-orgmode@gnu.org; Tue, 08 May 2012 10:15:23 -0400 Received: from g1t0027.austin.hp.com ([15.216.28.34]:5431) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRlC5-00006l-NS for emacs-orgmode@gnu.org; Tue, 08 May 2012 10:15:13 -0400 In-Reply-To: Message from Nicolas Goaziou of "Mon\, 07 May 2012 09\:10\:25 +0200." <87y5p44gbi.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: =?us-ascii?Q?=3D=3Futf-8=3FQ=3FFran=3DC3=3DA7ois=3F=3D?= Pinard , emacs-orgmode@gnu.org Nicolas Goaziou wrote: > Hello, >=20 > Fran=C3=A7ois Pinard writes: >=20 > > 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. >=20 > 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. >=20 > 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. >=20 Sorry I missed it and thanks for the clarification. Nick > On the other hand, every regular target will be invisible. Let me > explain. >=20 > At the moment, "<>" and "# <>" produce, respectively, " name=3D"tag" id=3D"tag">tag" and "". >=20 > In a not so distant future "<>" will produce " id=3D"tag">" and "# <>" will be ignored. >=20 > > I'll adapt of course, but to what? If not "# <>", then what is > > the way to create a named anchor at an arbitrary place in an Org file? >=20 > <> should suffice for that task. >=20 > I hope this is clearer now. >=20 >=20 > Regards, >=20 > --=20 > Nicolas Goaziou >=20