From: Carsten Dominik <dominik@science.uva.nl>
To: Wanrong Lin <wanrong.lin@gmail.com>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Feature improvement request: state change logging
Date: Fri, 13 Feb 2009 08:25:05 +0100 [thread overview]
Message-ID: <04073AA1-6DDA-45BC-848D-162B62079F3A@uva.nl> (raw)
In-Reply-To: <49930235.6050306@gmail.com>
On Feb 11, 2009, at 5:52 PM, Wanrong Lin wrote:
> Hi,
>
> My TODO sequence is set up as following:
>
> (setq org-todo-keywords '((sequence "TODO(t)" "STARTED(s!)"
> "WAITING(w@/!)" "MAYBE(m/!)" "DELEGATED(g@/!)" "DEFERRED(d!/!)"
> "HOLD(h!/!)" "|" "DONE(x)" "CANCELED(c)")))
>
> The state change logging is great, but I wonder whether we can
> further improve it:
>
> 1. Can we also include the original state in the log message?
> i.e.: instead of having - State "DEFERRED" [2009-02-11 Wed
> 11:38]
> we can have
> - State "DEFERRED" from "HOLD" [2009-02-11 Wed 11:38]
>
> The message will be clearer, and useful even when somebody edited
> the TODO keyword in place without using the "org-todo" command (in
> that case, simply looking at all the "destination states" in the log
> message does not give us the right information).
This strikes me like a useful idea, in particular if you are
jumping between states, or if only some states record logging info.
So I have added this capability. If you are configuring
the variable `org-log-note-headings', use the %S (capital S) as
a place holder for the old state.
> 2. Can we put all of those state change history logging messages
> into a drawer like "STATE-HIST" (when the drawer is defined in org-
> drawers), so it is less intrusive in the file?
I do like the idea to be able to put state changes into a drawer,
but I do not think that making it dependent on what it is org-drawers
is good. So lets use a separate variable:
If you configure org-log-state-notes-into-drawer, you can get all new
state changes into a drawer (sorry, no automatic wrapping of old ones).
Note that putting state log into a drawer will remove it from
export. If you want to export state changes, try
#+OPTIONS: d:("LOGBOOK")
> Thank you for giving a thought on it.
Thank you for contributing very good ideas!
- Carsten
prev parent reply other threads:[~2009-02-13 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 16:52 Feature improvement request: state change logging Wanrong Lin
2009-02-12 10:19 ` Ulf Stegemann
2009-02-12 17:51 ` Peter Jones
2009-02-13 7:25 ` Carsten Dominik [this message]
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=04073AA1-6DDA-45BC-848D-162B62079F3A@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=wanrong.lin@gmail.com \
/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).