From mboxrd@z Thu Jan 1 00:00:00 1970 From: david@adboyd.com (J. David Boyd) Subject: Re: timestamps and work logging Date: Tue, 06 Jun 2006 09:39:10 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fnbmb-0001Yu-Bk for emacs-orgmode@gnu.org; Tue, 06 Jun 2006 09:39:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fnbma-0001XO-N2 for emacs-orgmode@gnu.org; Tue, 06 Jun 2006 09:39:44 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fnbma-0001X8-GZ for emacs-orgmode@gnu.org; Tue, 06 Jun 2006 09:39:44 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Fnbtx-0000gB-Se for emacs-orgmode@gnu.org; Tue, 06 Jun 2006 09:47:22 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FnbmN-00062F-G8 for emacs-orgmode@gnu.org; Tue, 06 Jun 2006 15:39:31 +0200 Received: from 238-175.126-70.tampabay.res.rr.com ([70.126.175.238]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Jun 2006 15:39:31 +0200 Received: from david by 238-175.126-70.tampabay.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Jun 2006 15:39:31 +0200 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 David O'Toole writes: > Hi Carsten. I have another modest proposal for you :-) > > I notice that org-mode has a concept of timestamp ranges, and a > function to calculate the length of time in a given timestamp > range. > > It seems to me that with a small amount of additional work, org-mode > could: > > ... > > I originally looked at timeclock.el for this, and wrote a simple org > interface for it, but I want to keep the time logging information in > my org-files, next to each task description, and separated for each > client---not all bundled together in a huge ~/.timelog file. > > What do you think? Does it sound like a lot of work? > > -- > Dave O'Toole > dto@gnu.org I vote for this also. I used to use planner, and I liked being able to create a work report, but didn't care all that much for planner, or the fact that all the times were in a huge timelog file. Dave in Largo, FL