From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Clocking in the current task should clock it out first Date: Fri, 19 Mar 2010 18:36:02 +0100 Message-ID: References: <87sk7zt7w6.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NshIW-0001cC-HK for emacs-orgmode@gnu.org; Fri, 19 Mar 2010 14:51:52 -0400 Received: from [140.186.70.92] (port=50139 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NshIS-0001ZH-17 for emacs-orgmode@gnu.org; Fri, 19 Mar 2010 14:51:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NshIQ-0006RG-A1 for emacs-orgmode@gnu.org; Fri, 19 Mar 2010 14:51:47 -0400 Received: from mail-ew0-f224.google.com ([209.85.219.224]:58768) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NshIP-0006PF-DK for emacs-orgmode@gnu.org; Fri, 19 Mar 2010 14:51:46 -0400 Received: by mail-ew0-f224.google.com with SMTP id 24so703576ewy.15 for ; Fri, 19 Mar 2010 11:51:45 -0700 (PDT) In-Reply-To: <87sk7zt7w6.fsf@gollum.intra.norang.ca> 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: Bernt Hansen Cc: Org-mode Org-Mode Hi, strangely enough, this does not happen for me. Maybe you have some setup for clock resolution that I do not have? - Carsten On Mar 17, 2010, at 2:06 PM, Bernt Hansen wrote: > 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 =84Clock continues in "[task]"=93 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 =85 >> :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 =20= > but > I have auto clock resolution disabled so this is not leaving open =20 > clocks > in my setup. > > (setq org-clock-auto-clock-resolution nil) > > This of course is only a temporary work around until a real fix =20 > occurs. > I haven't had the time to investigate this yet but it is on my list of > things to look at. > > -Bernt > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten