From: "Gustav Wikström" <gustav@whil.se>
To: "sebastian.miele@gmail.com" <sebastian.miele@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Document level property drawer
Date: Wed, 2 Oct 2019 20:29:26 +0000 [thread overview]
Message-ID: <HE1PR02MB30332D112FE2944CB846675FDA9C0@HE1PR02MB3033.eurprd02.prod.outlook.com> (raw)
Hi Sebastian,
> From: Sebastian Miele
> Subject: Re: [O] [RFC] Document level property drawer
> Date: Tue, 01 Oct 2019 12:38:12 +0000
> ...
> I would like to be able to make a clear distinction between properties
> that are visible by default and properties that are not. Maybe it would
> be possible to allow some #+.. syntax following headings for subtree
> properties that are visible by default. A requirement could be made that
> such property specifications always have to be followed by a property
> drawer, even if that is empty. Then everything #+.. that is before the
> property drawer would belong to the heading/subtree, and everything #+..
> that follows the drawer would be treated as it is until now.
That maps quite well to what I also had in mind initially. What I
called "Document property keywords" in [fn:1]:
#+begin_quote
I propose to allow properties to be defined also as document
property keywords. All keywords in the top of a buffer, before any
non-comment line, are document-level keywords. In effect, they are
properties that apply in exactly the same way as properties defined
in the property drawer. The only reason for using a document keyword
instead of defining it inside the property drawer is to make it more
visible. One example would be the title-keyword (#+TITLE: ...).
#+end_quote
Although I didn't think of generalizing it to also work for the
outline nodes. Something that makes sense to do though, given the use
case you describe!
[fn:1] https://lists.gnu.org/archive/html/emacs-orgmode/2019-06/msg00000.html
FWIW
Gustav
next reply other threads:[~2019-10-02 20:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 20:29 Gustav Wikström [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-24 22:29 [RFC] Document level property drawer 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-06 6:02 Gustav Wikström
2019-10-06 5:35 Gustav Wikström
2019-10-05 18:20 Gustav Wikström
2019-10-06 0:51 ` Adam Porter
2019-09-30 22:09 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-09-29 10:27 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
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
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=HE1PR02MB30332D112FE2944CB846675FDA9C0@HE1PR02MB3033.eurprd02.prod.outlook.com \
--to=gustav@whil.se \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian.miele@gmail.com \
/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).