emacs-orgmode
[Top][All Lists]
Advanced

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

Re: [Orgmode] Possible bug in ordered tasks


From: Robert Goldman
Subject: Re: [Orgmode] Possible bug in ordered tasks
Date: Fri, 25 Jun 2010 09:48:42 -0500
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5

On 6/25/10 Jun 25 -9:12 AM, Carsten Dominik wrote:
> 
> On Jun 25, 2010, at 3:23 PM, Robert Goldman wrote:
> 
>> On 6/25/10 Jun 25 -2:03 AM, Carsten Dominik wrote:
>>> Hi Robert,
>>>
>>> On Jun 18, 2010, at 5:42 PM, Robert Goldman wrote:
>>>
>>>> I have found what I believe to be a bug in handling ordered subtasks.
>>>> Here is the behavior:
>>>>
>>>> I have a top level set of tasks that is ordered.
>>>>
>>>> One of the outline items below the top level set is a grab bag of tasks
>>>> that will be performed in parallel.  So this task is NOT ordered
>>>> (ORDERED: nil).
>>>>
>>>> The problem is that the blocking behavior from ordered tasks seems
>>>> to be
>>>> inherited from the top level task list into the second level of the
>>>> outline, even though the ORDERED property at the second level is
>>>> explicitly overridden.
>>>>
>>>> I am attaching an org file that displays this issue.  To see the
>>>> problem, put your cursor on the "Bar" task and attempt to change its
>>>> status to DONE.
>>>
>>> The problem here is that the value of the ORDERED property is the string
>>> "nil", and that is of course not nil!
>>>
>>> I have introduced a special case to have "nil" interpreted as nil here,
>>> because your use case makes a lot of sense.
>>
>> Oh, dear.  That makes perfect sense, now that I think of it.
>>
>> Question:  what is the proper way to get a NIL into a property?  Are we
>> to use () instead of "nil"?  Or are property values always interpreted
>> as strings?
>>
>> Apologies in advance if this is a stupid question!
> 
> Not a stupid question at all.
> 
> There is no way, currently.   Property values are string - the only way
> to make
> org-entry-get return nil is to not have the property defined at all.

OK, and there's no problem with this /except/ in cases where one wishes
to override inheritance, right?  I.e., you never need to specify nil at
the top level; it's only when you need to cancel a value that you are
inheriting....

best,
r




reply via email to

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