From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: blank todo kw does not delete closed ts Date: Thu, 11 Apr 2013 19:34:19 -0700 Message-ID: References: <87zjx6frrw.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:44797) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQTok-000619-1S for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 22:34:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UQToj-0002RU-0O for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 22:34:21 -0400 In-Reply-To: <87zjx6frrw.fsf@bzg.ath.cx> 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: Bastien Cc: emacs-orgmode@gnu.org Hi Bastien, On 4/10/13, Bastien wrote: >> Changing a doneified entry to blank todo state leaves a >> closed ts. >> >> #+BEGIN_SRC org >> ,* DONE doneify >> CLOSED: [2013-04-09 Tue 14:11] >> ,* now change to blank todo kw -- notice the closed ts >> CLOSED: [2013-04-09 Tue 14:11] >> #+END_SRC >> >> Perhaps it would be more intuitive for newcomers, and safer >> for expiry searches like "+CLOSED<\"<-1m>\"" where not >> everybody thinks to try to match all done todo keywords (not >> even sure what the convention is for that), to remove the >> ts. > > I'm not sure about this one. Seems logical to keep the CLOSED > information for tasks that have been done once and that do not > have (new) active TODO keywords yet. I think it depends on how you look at it. For a different use case from yours: I view blank entries as just another todo state. To me, I want the same behavior (deleting the closed timestamp because I *reversed* the doneification) for switching to blank as switching to any other todo state. This keeps things orthogonal and therefore predictable. The closed timestamp is not a notation (that is what state logs are for), but a semantic indication of closedness that is useful for expiry. Reversing the done should in my use case (but not yours) undo the closedness. I wanted to to expire closed entries, and did this: ("ne" "clean up by expired CLOSED" tags "+CLOSED<\"<-1m>\"" ((org-tags-match-list-sublevels nil) (org-agenda-sorting-strategy '(category-up user-defined-up)))) This will expire blank entries also. I thought closed = doneish because I prefer the orthogonal approach. I think some other users will also. Of course the user can try to figure out how to say TODO=done& (or something), but might not think to do so at first. I have never changed doneish to blank without having to delete the timestamp. I thought that was a bug and did not realize that you had a use case for making blank entries different from other todo states. FWIW. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is NO hope without action. This means YOU.