[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[O] About commit named "Allow multi-line properties to be specified in p

From: Nicolas Goaziou
Subject: [O] About commit named "Allow multi-line properties to be specified in property blocks"
Date: Mon, 31 Oct 2011 20:06:17 +0100


I just noticed that commit (8354fd9e0f5fff04665b2272fff6376b15ec0225).

Could we talk about it before pushing it, a few days before the release?

I am a bit worried about the new block types being introduced recently.
Some may be justified, I don't know yet, but "#+begin_property"
definitely isn't.

By looking at the Org syntax. what appears clearly is that Org blocks
are used for contents formatting. Center blocks, quote blocks, verse
blocks, special blocks, example blocks, export blocks, even src blocks
(even though these blocks may be used for very different things, they
exist primarily to display source code)... there's no exception.

On the other hand, Org internals are controlled through keywords,
property drawers, and options on blocks.

As "#+begin_property" block isn't about contents. I can't see any reason
for it to exist under this shape. So, again, can we discuss about
another approach that would not break the logic behind Org's syntax?

I don't fully grasp the problem it tries to solve, but what's wrong
with, for example, "#+property: var multiple couples"? What's wrong
with :var_list: x=1,y=3,z=4 in a property drawer? What's wrong
with #+header: :var x=1, y=2, z=3 just above the source block? As your
already know, #+header can span already on multiple lines.

Hoping we can find a more elegant solution,


Nicolas Goaziou

reply via email to

[Prev in Thread] Current Thread [Next in Thread]