Re: [O] blank todo kw does not delete closed ts
Hi Brian, Brian van den Broek brian.van.den.br...@gmail.com writes: Hi Bastien and all, I am afriad you saw this coming: I somehow was, but I played ostrich here :) Could that be an option? I actively would want to preserve the closed note to keep an accurate history of my work with the task. There is now `org-closed-keep-when-no-todo', defaulting to nil. Thanks, -- Bastien
Re: [O] blank todo kw does not delete closed ts
On 4/12/13, Bastien b...@gnu.org wrote: I'm convinved now, and switching to state without any TODO keyword will now remove the CLOSED planning information. Thanks, Bastien. One of the great things about Org is its attention to detail, and that includes little orthogonality pieces. 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.
Re: [O] blank todo kw does not delete closed ts
On 12 Apr 2013 11:58, Bastien b...@gnu.org wrote: Hi Samuel, I'm convinved now, and switching to state without any TODO keyword will now remove the CLOSED planning information. Thanks, -- Bastien Hi Bastien and all, I am afriad you saw this coming: Could that be an option? I actively would want to preserve the closed note to keep an accurate history of my work with the task. Best, Brian vdB
Re: [O] blank todo kw does not delete closed ts
Hi Samuel, I'm convinved now, and switching to state without any TODO keyword will now remove the CLOSED planning information. Thanks, -- Bastien
Re: [O] blank todo kw does not delete closed ts
Hi Bastien, On 4/10/13, Bastien b...@gnu.org 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.
Re: [O] blank todo kw does not delete closed ts
Hi Samuel, Samuel Wales samolog...@gmail.com writes: 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. -- Bastien
[O] blank todo kw does not delete closed ts
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. Thanks. 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.
