From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pete Ley Subject: Re: Org-mode Habit with Varying Description Date: Thu, 23 Oct 2014 20:42:01 -0700 Message-ID: <878uk6nng6.fsf@enterprise.sectorq.net> References: <87ppdmfxre.fsf@enterprise.sectorq.net> <87zjcqz2f2.fsf@ericabrahamsen.net> <87egu1zk8k.fsf@konixwork.incubateur.ens-lyon.fr> <87zjcpfksm.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55840) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XhVld-000647-U9 for emacs-orgmode@gnu.org; Thu, 23 Oct 2014 23:42:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XhVlU-00051J-S4 for emacs-orgmode@gnu.org; Thu, 23 Oct 2014 23:42:21 -0400 Received: from mail-pa0-x235.google.com ([2607:f8b0:400e:c03::235]:55278) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XhVlU-000512-L5 for emacs-orgmode@gnu.org; Thu, 23 Oct 2014 23:42:12 -0400 Received: by mail-pa0-f53.google.com with SMTP id kx10so336520pab.26 for ; Thu, 23 Oct 2014 20:42:10 -0700 (PDT) In-Reply-To: <87zjcpfksm.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 22 Oct 2014 00:29:45 +0800") 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: Eric Abrahamsen Cc: emacs-orgmode@gnu.org > All I've got now are a function that finds the logbook, and another that > parses the log items and normalizes them: extracts the TODO > states/timestamps/key-values and sets them as properties on the items > themselves. Then you've got a pretty good basis from which to do > reporting. > > Hooking into note-taking and todo state-change logging to prompt for > values should be easy. > > I don't know yet how to approach the reporting part, mostly because I > haven't sat down and thought about how this would be most useful. It > will also require reading org-clock and org-habit in detail -- clearly > reporting to a table like they do is the right way to go. > > How to get the most out of the data? I was thinking of having > COLUMN_FORMULA and TABLE_FORMULA properties on the heading. When you > report from the heading, each key in the logbook data creates a table > column. Each column formula property creates another column, populated > by that formula (presumably calculated from the data columns). Then the > table formula gets slapped on to the bottom of it, and the whole thing > runs. > > So if you had a heading like this: > > * TODO Anneal galoshes > :LOGBOOK: > GALOSHES: 15; CLOCK: [2014-10-15 Wed 09:07]--[2014-10-15 Wed 17:10] => 8:03 > GALOSHES: 13; CLOCK: [2014-10-14 Tue 08:50]--[2014-10-14 Tue 16:30] => 7:40 > GALOSHES: 14; CLOCK: [2014-10-13 Mon 09:30]--[2014-10-13 Mon 17:06] => 7:36 > :END: > > You'd end up with a table with two data columns. Then you could have a > COLUMN_FORMULA property that created a third column, displaying galoshes > annealed per hour. And a TABLE_FORMULA property that did... something... > with all that information. > > In a sense, it's a bit like column view, except using logbook data > rather than property values. This sounds pretty great. I'd like to see the functions you have anyway, seems like something the community might find useful. I know I could find a few use cases for it.