From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Gustav Wikström" <gustav@whil.se>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Proposal for new document-level syntax
Date: Mon, 03 Jun 2019 22:39:57 +0200 [thread overview]
Message-ID: <87ftoqv1wi.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <HE1PR02MB3033E7377E12EA99F18185E9DA1A0@HE1PR02MB3033.eurprd02.prod.outlook.com> ("Gustav Wikström"'s message of "Sat, 1 Jun 2019 23:08:52 +0000")
Hello,
Gustav Wikström <gustav@whil.se> writes:
> No worries. I think I explained but it can be further detailed. What I
> mean is that any property you can think of should be possible to add
> to a document as a keyword with the syntax:
>
> #+{PROPERTY}: {Value}
IIRC, Org uses
#+PROPERTY: {key} {value}
Why "should" it be possible to use a different syntax?
> But only at the beginning of a file, before any other content. The
> only reason for defining properties like that is for them to be
> visible outside of the property drawer. I'm thinking mostly of
> =#+TITLE= and similar keywords.
>
> I'd like to depricate =#+PROPERTY:= since it breaks the outline
> hierarchy and doens't follow the convention for how properties are
> defined inside headlines.
So the reason for this change is that keywords break the outline
hierarchy? Well, keywords do not belong to the outline hierarchy in the
first place. But syntax is not very different, either.
> Removing the "old" way of defining properties for the whole buffer
> will make property-syntax defined the same for documents and
> headlines. With the slight extention of allowing arbitrary keywords to
> stand for properties at the beginning of the buffer. Note that we
> already have "document property keywords" in org-mode. Less limited
> since they're not positionally contained. And only for a limited set
> of keywords; the "export keywords". (See [[info:org#Export Settings]])
"Document property keyword" has no syntactical meaning. It is used for
fontification.
> In my opinion property drawers is the improvement which in time will
> make the existing property-keyword redundant.
I still don't get how this is an improvement. What would you be able to
do with properties drawers that you cannot do currently with regular
keywords? This is a genuine question: I don't want to turn down your
suggestion, but I think it entails a lot of changes, and I want to be
sure there is a real benefit to it.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-06-03 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 10:15 Proposal for new document-level syntax Gustav Wikström
2019-06-01 13:17 ` Fraga, Eric
2019-06-01 13:45 ` Achim Gratz
2019-06-01 14:01 ` Fraga, Eric
2019-06-01 15:53 ` Gustav Wikström
2019-06-01 21:00 ` Nicolas Goaziou
2019-06-01 23:08 ` Gustav Wikström
2019-06-03 20:39 ` Nicolas Goaziou [this message]
2019-06-06 7:50 ` Gustav Wikström
2019-06-02 7:35 ` Norman Walsh
2019-06-02 22:49 ` Samuel Wales
2019-06-06 9:29 ` 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=87ftoqv1wi.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=gustav@whil.se \
/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).