From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Bug: Custom TODO fields not rendered when preceded by priority [9.1.14 (9.1.14-9-g131531-elpaplus @ /Users/michaeldickens/.emacs.d/elpa/org-plus-contrib-20181217/)] Date: Sun, 02 Feb 2020 08:42:01 +0100 Message-ID: <87y2tlbfli.fsf@bzg.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39628) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iy9tM-0001Pe-OC for emacs-orgmode@gnu.org; Sun, 02 Feb 2020 02:42:06 -0500 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-mx.org@gnu.org Sender: "Emacs-orgmode" To: Michael Dickens Cc: emacs-orgmode@gnu.org Hi Michael, Michael Dickens writes: > You could argue that this is expected behavior and the priority > should go after the to-do state, but IMO it should work either way > because it can still be unambiguously parsed. Org sets a few syntactic rules, the position of the priority cookie right _after_ the TODO keyword is one of them which we don't want to change, as it makes it easier for everyone to read Org files. Well, because a different syntax can be unambiguously parsed does not mean we should use this different syntax. Best, -- Bastien