From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: BUG-Resume clock on startup Date: Wed, 08 Jul 2009 07:40:08 -0400 Message-ID: <87skh72yjr.fsf@gollum.intra.norang.ca> References: <871vos3wk9.fsf@gollum.intra.norang.ca> <8FC593F5-EC24-4DC1-BCBC-B813131DAFE2@gmail.com> 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 1MOVVh-00083G-9n for emacs-orgmode@gnu.org; Wed, 08 Jul 2009 07:40:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOVVd-000804-Dj for emacs-orgmode@gnu.org; Wed, 08 Jul 2009 07:40:24 -0400 Received: from [199.232.76.173] (port=48996 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOVVd-000801-B3 for emacs-orgmode@gnu.org; Wed, 08 Jul 2009 07:40:21 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:56154) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MOVVd-0000a6-1Y for emacs-orgmode@gnu.org; Wed, 08 Jul 2009 07:40:21 -0400 In-Reply-To: <8FC593F5-EC24-4DC1-BCBC-B813131DAFE2@gmail.com> (Carsten Dominik's message of "Wed\, 8 Jul 2009 06\:56\:49 +0200") 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: Carsten Dominik Cc: emacs-orgmode@gnu.org Carsten Dominik writes: > On Jul 8, 2009, at 1:25 AM, Bernt Hansen wrote: > >> Hi Carsten, >> >> I have a monthly repeated task (Archive tasks) that has lots of old >> clock time on it currently but has never been marked DONE since the >> creation of the property LAST_REPEAT_TIME. If this task is clocking >> when Emacs exits and you restart emacs and answer Yes to continue the >> clock - the modeline has the total time for the parent task (151:04 >> instead of the total time for this task (5:04). If I clock the task >> in >> again the modeline is correct. > > I don't think this can be avoided for a transition period, until each > such tasks has the new property. > > O course you can go to all these tasks and add the LAST_REPEAT > property yourself. The bug isn't that the LAST_REPEAT is missing - but that the modeline has the total time for the parent task of the one that gets clocked in. -Bernt