emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Goldman <rpgoldman@sift.info>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Possible bug in ordered tasks
Date: Fri, 25 Jun 2010 09:48:42 -0500	[thread overview]
Message-ID: <4C24C1CA.2010407@sift.info> (raw)
In-Reply-To: <5896B53A-BDA5-4D02-9DD5-7121A8DB0165@gmail.com>

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	other threads:[~2010-06-25 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 15:42 Possible bug in ordered tasks Robert Goldman
2010-06-25  7:03 ` Carsten Dominik
2010-06-25 13:23   ` Robert Goldman
2010-06-25 14:12     ` Carsten Dominik
2010-06-25 14:48       ` Robert Goldman [this message]
2010-06-25 16:21         ` Carsten Dominik
2010-06-25 18:55       ` Bernt Hansen
2010-06-26  5:55         ` Carsten Dominik
2010-06-26 11:34           ` Bernt Hansen

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=4C24C1CA.2010407@sift.info \
    --to=rpgoldman@sift.info \
    --cc=carsten.dominik@gmail.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).