From: Eric Schulte <eric.schulte@gmx.com>
To: emacs-orgmode@gnu.org
Subject: Re: Setting multiple variables for code blocks in one property drawer
Date: Sat, 25 Feb 2012 12:11:18 -0700 [thread overview]
Message-ID: <87ipiuenjd.fsf@gmx.com> (raw)
In-Reply-To: 20120220114320.GA8866@client195-190.wlan.hu-berlin.de
Hi,
Viktor Rosenfeld <listuser36@googlemail.com> writes:
> Hi Eric,
>
> Eric Schulte wrote:
>
>> Viktor Rosenfeld <listuser36@googlemail.com> writes:
>>
>> > Hi Eric,
>> >
>> > thanks for your input. I just pulled the latest code from git and while
>> > my original example works, the following does not:
>> >
>> > :PROPERTIES:
>> > :var: foo=1
>> > :var+: bar=2
>> > :var+: baz=3
>> > :END:
>> >
>> > #+BEGIN_SRC sh
>> > echo foo: $foo
>> > echo bar: $bar
>> > echo baz: $baz
>> > #+END_SRC
>> >
>>
>> Thanks for reporting, I've just pushed up a fix for this bug.
>
> Thanks for your fix. The above example now works for me.
>
> However, I've noticed a problem with inheriting var properties. They are
> inherited in a child task only if the child task itself has no var
> property. Is this the intended behavior? See the example below.
>
Yes,
The example below is the intended behavior. The property mechanism is
not tailored to variable setting, but is rather a general mechanism for
the concatenation of property strings. Any property specification
unless it is postfixed with a "+" will /reset/ the value of that
property to its current value.
However try replacing
> :var: foo="a"
with
> :var+: foo="a"
which is valid and should work for your use case below.
There are still some lingering issues with inheritance and Org-mode
properties which I may try to address one of these days.
Cheers,
>
> Cheers,
> Viktor
>
> * Parent task
> :PROPERTIES:
> :var: foo="1"
> :var+: bar="2"
> :END:
> ** Child task without own properties
>
> #+BEGIN_SRC sh
> echo foo: $foo
> echo bar: $bar
> #+END_SRC
>
> #+RESULTS:
> | foo: | 1 |
> | bar: | 2 |
>
> ** Child task with own properties
> :PROPERTIES:
> :var: foo="a"
> :END:
>
> #+BEGIN_SRC sh
> echo foo: $foo
> echo bar: $bar
> #+END_SRC
>
> #+RESULTS:
> | foo: | a |
> | bar: | |
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-02-25 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 12:46 Setting multiple variables for code blocks in one property drawer Viktor Rosenfeld
2012-02-15 15:08 ` Eric Schulte
2012-02-15 19:12 ` Viktor Rosenfeld
2012-02-18 15:32 ` Eric Schulte
2012-02-20 11:43 ` Viktor Rosenfeld
2012-02-25 19:11 ` Eric Schulte [this message]
2012-02-27 7:00 ` Viktor Rosenfeld
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=87ipiuenjd.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
/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).