From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anupam Sengupta Subject: Re: Restarting a CLOCK entry? Date: Wed, 14 May 2008 12:43:13 -0700 Message-ID: References: <0F47B9F3-60F1-4D42-9695-859D35925744@uva.nl> 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 1JwMra-000096-II for emacs-orgmode@gnu.org; Wed, 14 May 2008 15:42:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JwMrY-00008n-Vn for emacs-orgmode@gnu.org; Wed, 14 May 2008 15:42:10 -0400 Received: from [199.232.76.173] (port=47768 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JwMrY-00008j-Qa for emacs-orgmode@gnu.org; Wed, 14 May 2008 15:42:08 -0400 Received: from main.gmane.org ([80.91.229.2]:34785 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 1JwMrY-0001jP-Eq for emacs-orgmode@gnu.org; Wed, 14 May 2008 15:42:08 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JwMrU-0004PV-Pi for emacs-orgmode@gnu.org; Wed, 14 May 2008 19:42:04 +0000 Received: from 216.138.123.172 ([216.138.123.172]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 May 2008 19:42:04 +0000 Received: from anupamsg by 216.138.123.172 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 May 2008 19:42:04 +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 [...] >> I sometimes CLOCK in a little later than the actual start (say 5-10 >> minutes after the fact) and then manually edit the start time on the >> entry. However, there does not seem to be a way to make Orgmode reset >> the clock and start from the edited entry. Carsten> Hi Anupam, Carsten> why does that bother you? yes, the clock time in the mode line Carsten> will be too short, but the time recorded in the buffer will be Carsten> correct when you stop the clock. Hi Carsten, The botheration is really a nag in the sense that the mode-line does not depict the correct elapsed time - I do use the mode line status (with other custom details) - and it will be nice to have the status line reflect the changes. Not a real deal-breaker - more of a nice to have function :-) Best Regards, -- Anupam