From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Wiegley Subject: Re: Clocking in the current task should clock it out first Date: Sun, 16 May 2010 13:15:53 -0400 Message-ID: <6B82E9E8-BB2A-4A48-8C42-B1C0FEB33904@gmail.com> References: <87sk7zt7w6.fsf@gollum.intra.norang.ca> <87k4t328a9.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=42740 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ODhRa-0005PY-Se for emacs-orgmode@gnu.org; Sun, 16 May 2010 13:16:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1ODhRY-0004CU-3o for emacs-orgmode@gnu.org; Sun, 16 May 2010 13:16:02 -0400 Received: from mail-px0-f169.google.com ([209.85.212.169]:61701) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1ODhRX-0004CK-UR for emacs-orgmode@gnu.org; Sun, 16 May 2010 13:16:00 -0400 Received: by pxi12 with SMTP id 12so4299595pxi.0 for ; Sun, 16 May 2010 10:15:58 -0700 (PDT) In-Reply-To: <87k4t328a9.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 , Carsten Dominik On Mar 22, 2010, at 8:25 PM, Bernt Hansen wrote: > I can't get the clock resolution/idle time code to do anything really > useful in my setup. If I do org-resolve-clocks when my current task = is > clocking it asks for how many minutes to keep etc, and then clocks in > from *now* leaving a hole in my clock data which I don't want. >=20 > I'm not sure exactly how this stuff is supposed to work - maybe John = can > shed some light on this. I can't find documentation about resolving > clocks in the regular org-mode documentation either. I remember an > article John posted on the mailing list but I don't think that got = into > the official org-mode documentation other than the lisp functions and > docstrings. Can you be a bit clearer here, Bernt? I use the clock resolver = constantly and have not been having the kinds of problem you describe. = I'd like to get these hammered out now, though. > I have also notice that clock resolution (in the distant past) would > overlap clock times. If it finds more than one open clock it can > resolve them so that they overlap with other clock entries and for me > that's _really_ _really_ bad. I'd rather have it to nothing than = create > hard-to-find overlapping clock entries. Yes, this is a possibility. :( Org-mode doesn't handle multiple open = clocks gracefully in other ways too, so I didn't try to hard to avoid = situations like these in the resolver. John=