From: "Daniel J. Sinder" <djsinder@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: logging transitional states
Date: Mon, 18 Dec 2006 18:14:25 -0800 [thread overview]
Message-ID: <45874B01.6070201@gmail.com> (raw)
In-Reply-To: <4dcc096c9d8ff094cf0253c47f874b87@science.uva.nl>
Just to add a related idea which may be relevant to a new extension:
Even for 'type' TODO keywords, they are asymmetric. There may be
any number of keywords that essentially mean 'to do', but only one
(DONE) that means 'done.'
I occasionally have TODO items that become moot or otherwise
uninteresting, but I want a record of the fact that they were
considered for action. For these, I don't want to remove the 'TODO'
keyword altogether. Rather, I could have keywords such as
WITHDRAWN, CANCELLED, SCRAPPED, etc. These items are no longer
things I need 'to do', nor are they truly 'done' (i.e., the task was
not completed), but I might want to keep them with a record (e.g., a
closing note) of why I scrapped the idea/plan.
So, combined with Dmitri's suggestion, I guess I'm suggesting that
TODO keywords should be assigned one of 3 mutually exclusive categories:
1. Nothing done yet
2. Transitional -- Action taken, but not yet done; in-progress
3. Nothing left to do (whether truly 'done' or not)
Anything in category 2 or 3 would be eligible for completion
logging. Anything in category 3 would not appear in agenda view
TODO lists, but could still be found via a TODO keyword search.
In an org file, they could be grouped like this:
#+TYP_TODO: {TODO NEXT MAYBE} {ORDERED PAYED RECEIVED} {DONE
WITHDRAWN SCRAPPED}
Dan
Carsten Dominik wrote:
> Currently there is not, but this looks like a useful extension.
>
> Forthcoming, some time next year.
>
>
> - Carsten
>
> On Dec 18, 2006, at 13:59, Dmitri Minaev wrote:
>
>> Hi,
>>
>> I use org-mode with TODO keywords denoting workflow states. E.g., when
>> tracking purchases, I set the keywords to:
>>
>> #+SEQ_TODO: TODO ORDERED INVOICE PAYED RECEIVED SENT
>>
>> Is there a way to log the dates not only for the completion (SENT
>> state), but also for all transitional states?
>>
>> Thank you.
>>
>> --
>> With best regards,
>> Dmitri Minaev
next prev parent reply other threads:[~2006-12-19 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 12:59 logging transitional states Dmitri Minaev
2006-12-18 15:27 ` Carsten Dominik
2006-12-19 2:14 ` Daniel J. Sinder [this message]
2006-12-19 4:29 ` Eddward DeVilla
2006-12-19 9:00 ` DSPAM " Bastien
2006-12-19 9:33 ` Carsten Dominik
2006-12-19 13:18 ` Dmitri Minaev
2006-12-19 17:22 ` Carsten Dominik
2006-12-19 12:04 ` Carsten Dominik
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=45874B01.6070201@gmail.com \
--to=djsinder@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).