emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: David O'Toole <dto@gnu.org>
To: emacs-orgmode@gnu.org
Subject: timestamps and work logging
Date: Tue, 06 Jun 2006 06:46:24 -0400	[thread overview]
Message-ID: <m31wu2k1dr.fsf@gnu.org> (raw)


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

next             reply	other threads:[~2006-06-06 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 10:46 David O'Toole [this message]
2006-06-06 13:39 ` timestamps and work logging J. David Boyd
2006-06-07 13:09 ` Carsten Dominik
2006-06-07 14:12   ` Jason F. McBrayer
2006-06-07 15:29     ` Xavier Maillard
2006-06-07 15:42       ` Carsten Dominik
2006-06-07 20:43         ` Jason F. McBrayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m31wu2k1dr.fsf@gnu.org \
    --to=dto@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).