From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: About commit named "Allow multi-line properties to be specified in property blocks" Date: Wed, 02 Nov 2011 16:35:22 +0100 Message-ID: <87hb2mo7ek.fsf@altern.org> References: <87vcr5c76e.fsf@gmail.com> <87vcr5j5a5.fsf@gmail.com> <4EAF118C.8050806@christianmoe.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:53856) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLczB-00078m-Ue for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 11:44:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLcz6-00064X-OZ for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 11:44:17 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:49176) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLcz6-00064N-J8 for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 11:44:12 -0400 Received: by wwe3 with SMTP id 3so350015wwe.30 for ; Wed, 02 Nov 2011 08:44:11 -0700 (PDT) In-Reply-To: <4EAF118C.8050806@christianmoe.com> (Christian Moe's message of "Mon, 31 Oct 2011 22:22:20 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: mail@christianmoe.com Cc: Nicolas Goaziou , Org Mode List Dear all, here is my take on this issue. First of all, sorry that the #+begin_property caused confusion, I'm the one responsible as I suggested this suggestion to Eric. I can see three issues: 1) Consistent syntax for #+xxx and #+begin_xxx? Nicolas point is valid -- #+begin_xxx syntax is about content and formatting, not about Org's internal. #+xxx is mostly about Org's internals (#+author, #+date, #+property, etc) and sometimes about content, as a convenient way of inserting one-line content block (#+html, #+LaTeX, etc) #+begin_property does not fit well into this picture. 2) "Cumulative properties"? Org's manual describes #+property like this: `#+PROPERTY: Property_Name Value' This line sets a default inheritance value for entries in the current buffer, most useful for specifying the allowed values of a property. Note that #+property: var foo=1 does *not* fit into the syntax described above. It is more something like `#+PROPERTY: var Variable_Name=Value' Hence the problem of accumulating the "values" of "var", which is not really a property name, but some syntactic clue to bind Variable_Name to its value. Here is a suggestion: use a syntaxe like #+var: foo 1 The difference between #+property and #+var would be that #+var is for setting general purpoes (elisp) variables, while #+property is for Org internals. Sorry if such a proposal has already been made and discussed. My feeling is that `org-accumulated-properties-alist' is complex and can be avoided -- but I need to think more about this. 3) Wrapping/folding long #+xxx lines? This is an independant request -- see Robert McIntyre's recent question on the list. The problem is that fill-paragraph on long #+xxx lines breaks the line into comment lines, which is wrong. Filling like this: #+TBLFM: @3$1=@1$1+@2$1::@3$2=@1$2+@2$2::...::... : @3$2=@1$2+@2$2::... : @3$2=@1$2+@2$2::... would feel more natural, at least to me. But maybe generalizing the #+begin_xxx syntax for *all* #+xxx keywords. This would make the current org-internals-oriented/content-oriented difference between #+xxx and #+begin_xxx obsolete, but this would spare us the cost of new syntax. Curious about input about this as well. Cheers, -- Bastien