From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: org-log-done vs. State Logbook Date: Sun, 04 Jan 2015 12:45:02 +0800 Message-ID: <87r3vb9msx.fsf@ericabrahamsen.net> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49363) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y7cyB-00051b-8v for emacs-orgmode@gnu.org; Sat, 03 Jan 2015 23:39:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y7cy5-0003Lk-CL for emacs-orgmode@gnu.org; Sat, 03 Jan 2015 23:39:15 -0500 Received: from plane.gmane.org ([80.91.229.3]:42386) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y7cy5-0003LY-5i for emacs-orgmode@gnu.org; Sat, 03 Jan 2015 23:39:09 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Y7cy3-0001Mj-Ki for emacs-orgmode@gnu.org; Sun, 04 Jan 2015 05:39:07 +0100 Received: from 222.129.224.90 ([222.129.224.90]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 04 Jan 2015 05:39:07 +0100 Received: from eric by 222.129.224.90 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 04 Jan 2015 05:39:07 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Yuri Niyazov writes: > Hi everyone, > > > So, I am trying to learn org-mode and figure out what's best for me. > One of the things that I would like to see is how long a TODO task > takes to travel through my life, on average from the moment when it is > captured, to scheduled, to done. Does something like this already > exists? > > One of the things I learned earlier today from this thread > https://lists.gnu.org/archive/html/emacs-orgmode/2011-10/msg00112.html > was that there's nothing that allows you to log state at the moment of > capture, so I created a capture template with a LOGBOOK drawer > included with an initial state change, like this: > > "* TODO %? > SCHEDULED: %^t > :LOGBOOK: > - State \"CAPTURED\" from \"\" %u > :END:" > > Now, one of the things that I am finding hard to figure out is what to > do at the end: there's both the ability to log when the object is done > using org-log-done, and one can also track every state change, which > includes the final state change of being done, with LOGBOOK state > changes. I am leaning towards turning them both on going forward, but > I have a bunch of old tasks, and some of them only have the CLOSED: > [timestamp] entry, and some of them only have the -State "DONE" from > "TODO" line in Logbook, and I don't know whether to invest the time > into fixing up the old entries to mirror the existing ones. The answer > to this depends on whether a package for for displaying statistics to > me already exists, and if it depends on one of those (CLOSED entry vs. > Logbook state changes). > > I know about clocktable, but clocktable seems to only be for > Clocking-in and Clocking-out entries, not across the lifetime of a > task. You could maybe take a look at org-habit? I haven't really used it, so I can't tell you about its ins and outs, but it might be useful. On the other hand, it seems to be mostly for repeating habits. Dunno what else there is...