From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: About commit named "Allow multi-line properties to be specified in property blocks" Date: Tue, 01 Nov 2011 13:02:05 -0600 Message-ID: <8762j3hdjm.fsf@gmail.com> References: <87vcr5c76e.fsf@gmail.com> <87vcr5j5a5.fsf@gmail.com> <8762j4evjl.fsf@gmail.com> <87k47kkfwp.fsf@gmail.com> <87y5w0ckt7.fsf@gmail.com> <87ty6ock7z.fsf@gmail.com> <87pqhbj4f3.fsf@gmail.com> <871utrj1hk.fsf@gmail.com> <87r51rhj9o.fsf@gmail.com> <4EB030D1.1070903@christianmoe.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([140.186.70.92]:41571) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLJhk-0007hI-Rk for emacs-orgmode@gnu.org; Tue, 01 Nov 2011 15:09:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLJhi-0004yp-TQ for emacs-orgmode@gnu.org; Tue, 01 Nov 2011 15:09:00 -0400 Received: from mail-gy0-f169.google.com ([209.85.160.169]:42776) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLJhi-0004yd-PU for emacs-orgmode@gnu.org; Tue, 01 Nov 2011 15:08:58 -0400 Received: by gyg10 with SMTP id 10so354453gyg.0 for ; Tue, 01 Nov 2011 12:08:57 -0700 (PDT) In-Reply-To: <4EB030D1.1070903@christianmoe.com> (Christian Moe's message of "Tue, 01 Nov 2011 18:48:01 +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: Org Mode List , Nicolas Goaziou --=-=-= Content-Type: text/plain Christian Moe writes: > On 11/1/11 5:58 PM, Eric Schulte wrote: > >>>> so assuming "var" is an accumulating property, then >>>> >>>> #+property: var foo=1 >>>> #+property: var bar=2 >>>> >>>> would result in `org-file-properties' having the following value >>>> >>>> (("var" . "foo=1 bar=1")) > > Given this: > > --- > > > #+property: var foo=1 > #+property: var bar=2 > > * Heading > :PROPERTIES: > :var: foo=3 > :END: > > > --- > > Would it result in (("var" . "foo=3 bar=2"))? > Good catch Christian, I get the following behavior, currently seems the property-block specification overwrites the global property. I'll have to update my patch to append at the subheading level as well. --=-=-= Content-Type: text/x-org Content-Disposition: inline; filename=something.org #+property: var foo=1 #+property: var bar=2 #+begin_src emacs-lisp (+ foo bar) #+end_src #+results: : 3 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2 * heading :PROPERTIES: :var: foo=4 :END: #+begin_src emacs-lisp foo #+end_src #+results: : 4 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=4 --=-=-= Content-Type: text/plain As for variable handling, I think the solution is to ensure that on the code-block side of things, a var string like "foo=3, bar=2, foo=1" results in, foo=1 bar=2 that is, subtree variable definitions will pre-empty earlier definitions of the same variable.. Best -- Eric > > Yours, > Christian -- Eric Schulte http://cs.unm.edu/~eschulte/ --=-=-=--