From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Bug: Priorities not inheriting [8.3.1 (8.3.1-56-g17a225-elpa @ /Users/luke/.emacs.d/elpa/org-20150817/)] Date: Wed, 19 Aug 2015 13:24:47 +0200 Message-ID: <871tez5xmo.fsf@gnu.org> References: <87wpwrab3l.fsf@nicolasgoaziou.fr> <87fv3fmvmz.fsf@gnu.org> <87fv3fa7rh.fsf@nicolasgoaziou.fr> <8737zfa6hm.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44174) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZS1UE-0006Q9-B8 for emacs-orgmode@gnu.org; Wed, 19 Aug 2015 07:24:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZS1UB-0000iZ-2s for emacs-orgmode@gnu.org; Wed, 19 Aug 2015 07:24:54 -0400 Received: from so1.mailgun.net ([198.61.254.11]:47037) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZS1UA-0000iE-Tw for emacs-orgmode@gnu.org; Wed, 19 Aug 2015 07:24:50 -0400 In-Reply-To: <8737zfa6hm.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 19 Aug 2015 12:59:49 +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: Nicolas Goaziou Cc: org-mode Mode , Luke Amdor Nicolas Goaziou writes: > Correcting myself, > >> AFAIK, PRIORITY never was intended to be inherited. Inheritance applies >> to node properties, i.e. property drawers, whereas special properties, >> like PRIORITY are, by definition, not set through property drawers. > > This is incorrect. What I mean is inheritance is not automatic for > special properties, unlike to regular node properties. > > In any case, this doesn't depend on `org-use-property-inheritance'. Few > of the special properties are inherited, e.g., BLOCKED, and /always/ > are, most are never inherited, e.g. ITEM. > >> There is also a technical issue: Org defines a default priority, so >> PRIORITY is never empty. Again, inheritance kicks in when a property is >> undefined at some level. This never happens in this case. > > We need to redefine `org-default-prority' to solve this, e.g., the > variable only applies to top-level items. After a few tests, I'm confused and I don't understand all the changes in this area (and they are not documented in ORG-NEWS.) Let's forget about what "special" means and how properties are displayed and set in the buffer. We have four categories of properties: 1. those which are *never* inherited (like ITEM) 2. those which are *always* inherited (like CATEGORY) 3. those which inheritance relies on `org-use-property-inheritance' 4. those which are not part of the previous types (4) sounds a bit borgesian, but it's important: my understanding is that this fourth category *should* be empty. Apparently it is not empty, since the PRIORITY property inheritance is not controlled by `org-use-property-inheritance'. Are there other exceptions? There is a default priority the same way there is a default category: having a default value for the PRIORITY property should not prevent inheriting it from a superior headline IMO, and the previous behavior was right. I know dwelling on this is boring but we need to do so, at least to clarify changes in etc/ORG-NEWS. Thanks, -- Bastien