From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Wahl Subject: Re: [RFC] Document level property drawer Date: Wed, 02 Oct 2019 12:29:30 +0200 Message-ID: <84eezvmodx.fsf@gmail.com> References: <87eezxrcwv.fsf@alphapapa.net> <84tv8tjywm.fsf@gmail.com> <87pnjgk1tz.fsf@alphapapa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:55863) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iFbt7-0007Qs-GH for emacs-orgmode@gnu.org; Wed, 02 Oct 2019 06:29:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iFbt6-0004WQ-Ac for emacs-orgmode@gnu.org; Wed, 02 Oct 2019 06:29:41 -0400 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:33338 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iFbt6-0004VU-3w for emacs-orgmode@gnu.org; Wed, 02 Oct 2019 06:29:40 -0400 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iFbt3-000lAS-AN for emacs-orgmode@gnu.org; Wed, 02 Oct 2019 12:29:37 +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" To: emacs-orgmode@gnu.org Adam Porter writes: > Marco Wahl writes: > >> Adam Porter writes: >> >>> Gustav Wikström writes: >>> >>>> 3) Properties defined in a property drawer will have precedence over >>>> properties defined as a property keyword, if the same property is >>>> defined using both conventions. >>> >>> That protocol seems unnatural and confusing to me: >>> >>> - If precedence were to be defined by something other than file-order, >>> it seems to me that those defined with #+ keywords should have >>> precedence, because they are more visible, while those in drawers are >>> hidden. >>> - However, it seems to me that the simplest, most natural protocol would >>> be for later declarations to override earlier ones. >> >> I think it would be quite natural to use the tree structure of Org. A >> property setting in a subtree overrides the setting in a parent (which >> could be the document(= the whole file.)) > > Hi Marco, > > I think you misunderstood his point #3 and my objection to it. :) Hi Adam, that's possible but I don't think so. But I'm willing to learn if I didn't get it. :) Possibly a concrete example can help. Let's take Org property CATEGORY for illustration. First to Gustav's statement 3): Let the file be this: --8<---------------cut here---------------start------------->8--- #+title: file :PROPERTIES: :CATEGORY: cat-doc-prop-drawer :END: * foo SCHEDULED: <2019-10-02 Wed> #+CATEGORY: cat-doc-prop-keyword-1 ** bar :somedrawer: #+CATEGORY: cat-doc-prop-keyword-2 :END: --8<---------------cut here---------------end--------------->8--- With Gustav's proposition the CATEGORY of task foo is cat-doc-prop-drawer. Next to your statements: You say the visibility is better for the #+-property keywords. I say they can occur _anywhere_ in the file and even in some drawers. See above "#+CATEGORY: cat-doc-prop-keyword-2". Further you say >>> - However, it seems to me that the simplest, most natural protocol would >>> be for later declarations to override earlier ones. This means that cat-doc-prop-keyword-2 from the example defines the CATEGORY property which at least I find not so natural. And I already stated what I find natural. Best regards, Marco