From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Fran=C3=A7ois_Pinard?= Subject: Re: "# <>" should stick to the following text Date: Sun, 06 May 2012 20:41:13 -0400 Message-ID: <86wr4orffa.fsf@mercure.progiciels-bpi.ca> References: <8662c9rqtq.fsf@mercure.progiciels-bpi.ca> <87397dgg9a.fsf@gmail.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]:59040) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRC0r-0003jz-TG for emacs-orgmode@gnu.org; Sun, 06 May 2012 20:41:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SRC0q-0000f0-7P for emacs-orgmode@gnu.org; Sun, 06 May 2012 20:41:17 -0400 Received: from 206-248-137-202.dsl.teksavvy.com ([206.248.137.202]:52218 helo=mercure.progiciels-bpi.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRC0q-0000ep-1Z for emacs-orgmode@gnu.org; Sun, 06 May 2012 20:41:16 -0400 In-Reply-To: <87397dgg9a.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 06 May 2012 23:18:41 +0200") 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: emacs-orgmode@gnu.org Nicolas Goaziou writes: > "# <>" is a deprecated construct. Sigh! I just spent a few hours adding many of those and making sure everything is regular. 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 not ultra clear to me, my English is not ultra solid either. I interpreted it as meaning that the preferred way for a text link was such "# <>" constructs, that is, all the contrary of a deprecation. > I suggest to avoid bothering with it. 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? Explicit HTML code? That does not look at all like an improvement: 1. it would be limited to HTML, 2. Org will not likely not follow links to these from within Emacs, 3. if explicit HTML is introduced through specialized Org comments, they suffer exactly from the edit problem "# <>" demonstrated, being tied to the preceding text instead of the following text. So, Nicolas, I would surely avoid bothering with this problem, but I do not feel I have that choice (yet). I hope the letter I wrote at the beginning of this little thread is not going to be dismissed or ignored. Fran=C3=A7ois