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: Mon, 07 May 2012 12:52:26 -0400 Message-ID: <861umw3pdh.fsf@mercure.progiciels-bpi.ca> References: <8662c9rqtq.fsf@mercure.progiciels-bpi.ca> <87397dgg9a.fsf@gmail.com> <86wr4orffa.fsf@mercure.progiciels-bpi.ca> <87y5p44gbi.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]:51347) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRRAk-0000A6-J6 for emacs-orgmode@gnu.org; Mon, 07 May 2012 12:52:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SRRAi-0006P9-Ud for emacs-orgmode@gnu.org; Mon, 07 May 2012 12:52:30 -0400 Received: from 206-248-137-202.dsl.teksavvy.com ([206.248.137.202]:56874 helo=mercure.progiciels-bpi.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRRAi-0006P2-Oa for emacs-orgmode@gnu.org; Mon, 07 May 2012 12:52:28 -0400 In-Reply-To: <87y5p44gbi.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 07 May 2012 09:10:25 +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: > 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. It might be worth making the manual clear, so users know what's happening, and what is worth pursuing and avoiding. > At the moment, "<>" and "# <>" produce, respectively, " name=3D"tag" id=3D"tag">tag" and "". > In a not so distant future "<>" will produce " id=3D"tag">" and "# <>" will be ignored. And one will be able to use <> anywhere, would it be at the beginning of a header of sentence. That would solve all my problems! So I'm eagerly awaiting for that "a not so distant future" to turn into "a recent past" :-). Thanks for the clarification. > I hope this is clearer now. In this message, yes. In the manual, not yet! Fran=C3=A7ois