From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulf Stegemann Subject: Re: Feature improvement request: state change logging Date: Thu, 12 Feb 2009 11:19:22 +0100 Message-ID: References: <49930235.6050306@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LXYfR-0006u8-RZ for emacs-orgmode@gnu.org; Thu, 12 Feb 2009 05:19:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LXYfR-0006tm-4G for emacs-orgmode@gnu.org; Thu, 12 Feb 2009 05:19:37 -0500 Received: from [199.232.76.173] (port=33495 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LXYfQ-0006th-Qz for emacs-orgmode@gnu.org; Thu, 12 Feb 2009 05:19:36 -0500 Received: from main.gmane.org ([80.91.229.2]:57631 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LXYfQ-0004Ty-3C for emacs-orgmode@gnu.org; Thu, 12 Feb 2009 05:19:36 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LXYfL-00029j-4l for emacs-orgmode@gnu.org; Thu, 12 Feb 2009 10:19:31 +0000 Received: from london.zeitform.net ([146.140.213.100]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 12 Feb 2009 10:19:31 +0000 Received: from ulf-news by london.zeitform.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 12 Feb 2009 10:19:31 +0000 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Wanrong Lin wrote: > 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] Nice idea IMHO. > 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? That's even better. I'd strongly second that. Ulf