From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: timestamps and work logging Date: Wed, 7 Jun 2006 15:09:30 +0200 Message-ID: <1e5be28f675e4f694864904f7091c988@science.uva.nl> References: Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fnxmy-0007FA-Nx for emacs-orgmode@gnu.org; Wed, 07 Jun 2006 09:09:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fnxmy-0007Ex-6q for emacs-orgmode@gnu.org; Wed, 07 Jun 2006 09:09:36 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fnxmx-0007Eu-TL for emacs-orgmode@gnu.org; Wed, 07 Jun 2006 09:09:35 -0400 In-Reply-To: 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: David O'Toole Cc: emacs-orgmode@gnu.org Interesting functionality and not hard to do - I am putting it on my list, but I am not sure how quickly this will happen. - Carsten On Jun 6, 2006, at 12:46, David O'Toole wrote: > > 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: > > 1. Provide a function org-clock-in, which lets you signal that you > have started working on a particular task. This would start a > timestamp range going on that task, so when you clock in on task > Foo, you get > > ** TODO Foo > WORK: <2006-06-06 Tue 06:33>--<> > > 2. Provide a function org-clock-out, which remembers where you last > clocked in, and completes the timestamp range: > > ** TODO Foo > WORK: <2006-06-06 Tue 06:33>--<2006-06-06 Tue 06:35> > > 3. Produce another timestamp range when you clock in again, thus > recording all the time intervals when you worked on this task: > > ** TODO Foo > WORK: <2006-06-06 Tue 06:33>--<2006-06-06 Tue 06:35> > WORK: <2006-06-06 Tue 06:39>--<> > > 4. Clock out of task A if you clock in to task B without manually > clocking out of task A. > > 5. Optionally display work time (i.e. no task completion) when > log-mode is on in the Agenda buffer. > > 6. When you call org-clock-total in a particular org-file, sum the > time intervals for each task in the file and produce a line like > > TOTALWORK: 3:14 (3 hours, 14 minutes) > > (This would make it easy for me to scan the file and produce client > bills from the output.) > > 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 > > > _______________________________________________ > Emacs-orgmode mailing list > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > > -- Carsten Dominik Sterrenkundig Instituut "Anton Pannekoek" Universiteit van Amsterdam Kruislaan 403 NL-1098SJ Amsterdam phone: +31 20 525 7477