From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: "# <>" should stick to the following text Date: Mon, 07 May 2012 09:10:25 +0200 Message-ID: <87y5p44gbi.fsf@gmail.com> References: <8662c9rqtq.fsf@mercure.progiciels-bpi.ca> <87397dgg9a.fsf@gmail.com> <86wr4orffa.fsf@mercure.progiciels-bpi.ca> 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]:45224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRI8E-0003Fp-Js for emacs-orgmode@gnu.org; Mon, 07 May 2012 03:13:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SRI8C-0005dd-RD for emacs-orgmode@gnu.org; Mon, 07 May 2012 03:13:18 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:37703) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRI8C-0005dH-Gl for emacs-orgmode@gnu.org; Mon, 07 May 2012 03:13:16 -0400 Received: by werc12 with SMTP id c12so162851wer.0 for ; Mon, 07 May 2012 00:13:14 -0700 (PDT) In-Reply-To: <86wr4orffa.fsf@mercure.progiciels-bpi.ca> (=?utf-8?Q?=22Fran?= =?utf-8?Q?=C3=A7ois?= Pinard"'s message of "Sun, 06 May 2012 20:41:13 -0400") 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: =?utf-8?Q?Fran=C3=A7ois?= Pinard Cc: emacs-orgmode@gnu.org Hello, Fran=C3=A7ois Pinard 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, "<>" and "# <>" produce, respectively, "tag" and "". In a not so distant future "<>" will produce "" and "# <>" will be ignored. > 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? <> should suffice for that task. I hope this is clearer now. Regards, --=20 Nicolas Goaziou