From mboxrd@z Thu Jan 1 00:00:00 1970 From: david@adboyd.com (J. David Boyd) Subject: clocking time Date: Wed, 15 Nov 2006 15:02:21 -0500 Message-ID: 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 1GkQyy-0005De-Sg for emacs-orgmode@gnu.org; Wed, 15 Nov 2006 15:03:40 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GkQyu-0005Cy-EG for emacs-orgmode@gnu.org; Wed, 15 Nov 2006 15:03:40 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GkQyu-0005Cv-Ay for emacs-orgmode@gnu.org; Wed, 15 Nov 2006 15:03:36 -0500 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 1GkQyt-0008M3-63 for emacs-orgmode@gnu.org; Wed, 15 Nov 2006 15:03:35 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GkQyL-0002eC-5A for emacs-orgmode@gnu.org; Wed, 15 Nov 2006 21:03:01 +0100 Received: from 10-169.35-65.tampabay.res.rr.com ([65.35.169.10]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 15 Nov 2006 21:03:01 +0100 Received: from david by 10-169.35-65.tampabay.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 15 Nov 2006 21:03:01 +0100 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 When I have a TODO item, and I've added time to it by clocking in and out, what happens if I reschedule that item for the next day, to continue working on it, then again clock time in and out? I should say, what is going to happen to the dynamic clock block I have placed at the top of the file. Actually, I guess I'll find out tomorrow when I use this, but I am curious. I made my subtree start with 'Nov 15', and then plan on making subsequent trees at the same level as 'Nov 16', 'Nov 17', etc. Then, I put what I am working on, or planning on working on, into a given day. Come to think of it, that's not a good way to do this, is it. I should have a better topic than the date. Or should I? I've seen some threads on this before, I believe, but since I wasn't doing it at the time, I wasn't able to follow them very well. Any ideas on the best structure for tracking programming work and priorities? Is this list archived somewhere? Dave