From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Document level property drawer
Date: Wed, 02 Oct 2019 12:29:30 +0200 [thread overview]
Message-ID: <84eezvmodx.fsf@gmail.com> (raw)
In-Reply-To: 87pnjgk1tz.fsf@alphapapa.net
Adam Porter <adam@alphapapa.net> writes:
> Marco Wahl <marcowahlsoft@gmail.com> writes:
>
>> Adam Porter <adam@alphapapa.net> writes:
>>
>>> Gustav Wikström <gustav@whil.se> 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
next prev parent reply other threads:[~2019-10-02 10:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 10:27 [RFC] Document level property drawer Gustav Wikström
2019-09-29 19:13 ` Marco Wahl
2019-09-30 16:01 ` Adam Porter
2019-09-30 20:46 ` Marco Wahl
2019-10-01 12:38 ` Sebastian Miele
2020-01-13 21:52 ` Marco Wahl
2020-01-15 8:18 ` Sebastian Miele
2020-02-01 19:59 ` Marco Wahl
2019-10-01 13:55 ` Adam Porter
2019-10-02 10:29 ` Marco Wahl [this message]
2019-10-03 18:06 ` Adam Porter
2019-10-04 11:05 ` Marco Wahl
2019-10-06 1:05 ` Adam Porter
2019-10-06 5:10 ` Matt Price
2019-10-15 17:49 ` Gustav Wikström
2019-10-16 0:48 ` Adam Porter
2019-10-16 9:48 ` Marco Wahl
2020-01-20 3:27 ` [Question] adding document global properties drawer stardiviner
2020-01-21 16:40 ` Nicolas Goaziou
2020-01-22 16:28 ` stardiviner
2020-01-24 23:14 ` Nicolas Goaziou
2020-02-23 7:31 ` [SOLVED] " stardiviner
2020-02-23 13:14 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2019-09-30 22:09 [RFC] Document level property drawer Gustav Wikström
2019-10-03 18:31 ` Adam Porter
2019-10-04 10:38 ` Marco Wahl
2019-10-06 1:01 ` Adam Porter
2019-10-07 7:46 ` Marco Wahl
2019-10-02 20:29 Gustav Wikström
2019-10-05 18:20 Gustav Wikström
2019-10-06 0:51 ` Adam Porter
2019-10-06 5:35 Gustav Wikström
2019-10-06 6:02 Gustav Wikström
2019-10-20 2:28 Gustav Wikström
2019-10-22 21:24 ` Marco Wahl
2019-10-23 8:43 ` Marco Wahl
2019-10-23 8:59 ` Gustav Wikström
2019-10-24 21:01 ` Gustav Wikström
2019-10-25 12:58 ` Marco Wahl
2019-10-23 16:08 ` Adam Porter
2019-10-24 22:29 Gustav Wikström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84eezvmodx.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).