From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Clocking in the current task should clock it out first Date: Wed, 17 Mar 2010 09:06:17 -0400 Message-ID: <87sk7zt7w6.fsf@gollum.intra.norang.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NrsxM-0005Km-4r for emacs-orgmode@gnu.org; Wed, 17 Mar 2010 09:06:40 -0400 Received: from [140.186.70.92] (port=47140 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NrsxK-0005KC-UW for emacs-orgmode@gnu.org; Wed, 17 Mar 2010 09:06:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NrsxJ-0002g4-AX for emacs-orgmode@gnu.org; Wed, 17 Mar 2010 09:06:38 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:61833) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NrsxJ-0002f0-8J for emacs-orgmode@gnu.org; Wed, 17 Mar 2010 09:06:37 -0400 In-Reply-To: (Daniel Clemente's message of "Wed\, 17 Mar 2010 10\:45\:27 +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: Daniel Clemente Cc: Org-mode Org-Mode Daniel Clemente writes: > Hi, > in recent org-modes a new behaviour was added: when doing C-c C-x > C-i on the current task, it isn't clocked out first. It shows the > message =E2=80=9EClock continues in "[task]"=E2=80=9C and adds a new line= for the > clock in. > This creates a clock section like: > > #+BEGIN_EXAMPLE > *** after pressing many successive C-c C-x C-i =E2=80=A6 > :CLOCK: > CLOCK: [2010-03-17 dc 10:25]--[2010-03-17 dc 10:30] =3D> 0:05 > CLOCK: [2010-03-17 dc 10:20] > CLOCK: [2010-03-17 dc 10:20] > CLOCK: [2010-03-17 dc 10:20] > CLOCK: [2010-03-17 dc 10:20] > CLOCK: [2010-03-17 dc 10:20] > CLOCK: [2010-03-17 dc 10:20] > CLOCK: [2010-03-12 dv 16:38]--[2010-03-12 dv 16:39] =3D> 0:01 > :END: > #+END_EXAMPLE > > > They are later correctly found to be dangling clocks. > I presume this is a bug? Hi Daniel, Yes I believe this is a bug. I think I've also run into this issue but I have auto clock resolution disabled so this is not leaving open clocks in my setup. (setq org-clock-auto-clock-resolution nil) This of course is only a temporary work around until a real fix occurs. I haven't had the time to investigate this yet but it is on my list of things to look at. -Bernt