From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [RFC] Properly handle keyword + COMMENT keyword Date: Fri, 11 Apr 2014 21:42:26 +0200 Message-ID: <8738hjk5zx.fsf@gmail.com> References: <87txanjn0i.fsf@gmail.com> <87sipkkiro.fsf@gmail.com> <87a9bs57cg.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34972) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WYhKu-0001ZO-6L for emacs-orgmode@gnu.org; Fri, 11 Apr 2014 15:42:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WYhKo-0004ZD-E7 for emacs-orgmode@gnu.org; Fri, 11 Apr 2014 15:42:04 -0400 In-Reply-To: <87a9bs57cg.fsf@bzg.ath.cx> (Bastien's message of "Fri, 11 Apr 2014 10:59:11 +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: Bastien Cc: Org Mode List Bastien writes: > Speaking of consistency, I noticed this minor glitch: > > * NEXT COMMENT A headline [0/2] > > - [ ] A > - [ ] B > > * NEXT [#A] [1/2] COMMENT Another headline > > - [X] A > - [ ] B > > See that the second COMMENT is not fontified and I think > it will not be processed correctly. > > Now that COMMENT will not be always the first word of a > headline, we should mention that TODO keywords and priority > cookies are allowed before a COMMENT keyword, while stats > cookies are not. (Or allow stats cookies for simplicity's > sake.) COMMENT has to be at the start of the headline text, which starts after any TODO keyword and priority character (see `org-heading-components'). So the COMMENT keyword in the second headline is not valid. The manual specifies: Also entire subtrees starting with the keyword =E2=80=98COMMENT=E2=80=99 = will never be exported We could be more explicit. In any case, COMMENT cannot be put anywhere. Regards, --=20 Nicolas Goaziou