From: Samuel Wales <samologist@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: blank todo kw does not delete closed ts
Date: Thu, 11 Apr 2013 19:34:19 -0700 [thread overview]
Message-ID: <CAJcAo8sNh_mcQEBvU+5V6hWcDng8qfuax+QQquJLcQ0+zBFHqg@mail.gmail.com> (raw)
In-Reply-To: <87zjx6frrw.fsf@bzg.ath.cx>
Hi Bastien,
On 4/10/13, Bastien <bzg@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.
next prev parent reply other threads:[~2013-04-12 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 22:13 blank todo kw does not delete closed ts Samuel Wales
2013-04-10 7:31 ` Bastien
2013-04-12 2:34 ` Samuel Wales [this message]
2013-04-12 2:38 ` Samuel Wales
2013-04-12 15:57 ` Bastien
2013-04-13 20:27 ` Samuel Wales
2013-04-14 2:23 ` Brian van den Broek
2013-04-14 8:53 ` Bastien
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=CAJcAo8sNh_mcQEBvU+5V6hWcDng8qfuax+QQquJLcQ0+zBFHqg@mail.gmail.com \
--to=samologist@gmail.com \
--cc=bzg@gnu.org \
--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).