From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Weissmann Subject: Re: Progress logging with org-mode Date: Thu, 4 Oct 2007 11:02:35 +0000 (UTC) Message-ID: References: <80f759140e2a298fcb4de1f0393987aa@science.uva.nl> <8cf58fad83b2db703178b52fd619fc51@science.uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IdOTx-0007fW-NN for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 07:03:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IdOTv-0007at-5a for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 07:03:04 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IdOTv-0007ab-0d for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 07:03:03 -0400 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IdOTu-0002x2-Gv for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 07:03:02 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IdOTh-0003bg-Tp for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 11:02:49 +0000 Received: from mail2.siscog.pt ([195.22.30.41]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Oct 2007 11:02:49 +0000 Received: from trmsw by mail2.siscog.pt with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Oct 2007 11:02:49 +0000 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 Carsten Dominik science.uva.nl> writes: > The point is that the next clock entry is inserted *before* the > previous ones, > and in my setting this does not change the indentation of the entries > that were > already there... But it only as long as they're not indented by some foolish user, afterwards. I confess I tweak, split and merge clocks quite a lot, as well as re-edit their notes, which is why I care about them having robust and consistent indentation. Very often I come back from a meeting, clock out, and then split the time between multiple tasks that happened to be treated by the meeting. It's probably cleaner to think of each meeting as an individual task, but when you're logging time with a view to billing, that's not always what you want. Cheers, Tom SW