From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Document level property drawer
Date: Fri, 04 Oct 2019 13:05:42 +0200 [thread overview]
Message-ID: <847e5kixdl.fsf@gmail.com> (raw)
In-Reply-To: 87muehbt5x.fsf@alphapapa.net
Adam Porter <adam@alphapapa.net> writes:
> Marco Wahl <marcowahlsoft@gmail.com> 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
next prev parent reply other threads:[~2019-10-04 11:05 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
2019-10-03 18:06 ` Adam Porter
2019-10-04 11:05 ` Marco Wahl [this message]
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=847e5kixdl.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).