From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Wahl Subject: Re: [RFC] Document level property drawer Date: Fri, 04 Oct 2019 13:05:42 +0200 Message-ID: <847e5kixdl.fsf@gmail.com> References: <87eezxrcwv.fsf@alphapapa.net> <84tv8tjywm.fsf@gmail.com> <87pnjgk1tz.fsf@alphapapa.net> <84eezvmodx.fsf@gmail.com> <87muehbt5x.fsf@alphapapa.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:47232) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iGLPE-0002Ae-73 for emacs-orgmode@gnu.org; Fri, 04 Oct 2019 07:05:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iGLPD-0008E2-1X for emacs-orgmode@gnu.org; Fri, 04 Oct 2019 07:05:52 -0400 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:59418 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iGLPC-0008D8-Qu for emacs-orgmode@gnu.org; Fri, 04 Oct 2019 07:05:50 -0400 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iGLPA-000L1n-4F for emacs-orgmode@gnu.org; Fri, 04 Oct 2019 13:05:48 +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: >> 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. > Org may allow #+KEYWORD: lines to appear anywhere in a file, including > in arbitrary drawers, but that's up to the user. If the user chooses to > hide them in drawers, it's his responsibility. > > AFAICT that's not a common or generally recommended thing to do. Most > Org files have such lines at the top of the file, and some under a > heading at the bottom of the file with other settings. Such lines don't > need to be in drawers, and this proposal wouldn't change that. > > So I think it would be confusing if settings in a drawer at the top of > the file were to absolutely override settings outside of drawers (which > would mean that hidden settings could override plainly visible ones). > The most natural protocol would be like written language: later > declarations override earlier ones. Hi Adam, Just I got the idea that for a good part this discussion is about personal preferences. For me for example it's not a big deal if a property is placed within a drawer or not. I don't care much about the "visibility" of a property setting. Of course I respect other views about this. What I really find irritating is that "Org ... allows #+KEYWORD: lines to appear anywhere in a file" (This sentence is from you) with the meaning that the settings apply to the whole file. I think this interpretation of #+KEYWORD: lines is unnecessary and confusing. BTW I find it completely natural that--let's for simplicity assume an Org file without any drawers--#+KEYWORD: settings that appear later in a file replace earlier settings. Best regards, -- Marco