From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Possible bug in ordered tasks Date: Fri, 25 Jun 2010 16:12:59 +0200 Message-ID: <5896B53A-BDA5-4D02-9DD5-7121A8DB0165@gmail.com> References: <4C1B93D4.1050000@sift.info> <4264D53A-92CE-43C1-A7CC-5526DDD90BC4@gmail.com> <4C24ADBD.3090204@sift.info> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=54743 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OSCyz-0004ra-1E for emacs-orgmode@gnu.org; Fri, 25 Jun 2010 13:46:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OS9ef-0007eF-34 for emacs-orgmode@gnu.org; Fri, 25 Jun 2010 10:13:18 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:64437) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OS9ee-0007cs-Si for emacs-orgmode@gnu.org; Fri, 25 Jun 2010 10:13:17 -0400 Received: by wyb39 with SMTP id 39so1661174wyb.0 for ; Fri, 25 Jun 2010 07:13:03 -0700 (PDT) In-Reply-To: <4C24ADBD.3090204@sift.info> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: rpgoldman@sift.info Cc: Org Mode 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. - Carsten