From mboxrd@z Thu Jan 1 00:00:00 1970 From: gregory@dynapse.com (Gregory J. Grubbs) Subject: Re: Patch for resolving "away time" when clocked in Date: Fri, 16 Oct 2009 12:09:12 -0600 Message-ID: <87zl7rky7r.fsf@dynapse.com> References: <27E1810B-0447-46B3-9AF4-BA14ACECA00A@gmail.com> <877huvmirr.fsf@dynapse.com> <131E75B1-D61D-46B6-A28A-F75F7CFE622E@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 1MyrFK-0000TY-Ml for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:09:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyrFF-0000SZ-VZ for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:09:46 -0400 Received: from [199.232.76.173] (port=38245 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyrFF-0000SP-Lm for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:09:41 -0400 Received: from lo.gmane.org ([80.91.229.12]:46312) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MyrFF-0001zG-A7 for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:09:41 -0400 Received: from list by lo.gmane.org with local (Exim 4.50) id 1MyrF6-0008IL-Pw for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 20:09:32 +0200 Received: from 72.42.83.192 ([72.42.83.192]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Oct 2009 20:09:32 +0200 Received: from gregory by 72.42.83.192 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Oct 2009 20:09:32 +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: emacs-orgmode@gnu.org John Wiegley writes: > On Oct 16, 2009, at 11:59 AM, Gregory J. Grubbs wrote: > >> One suggestion: I think when your code stops on a clock and prompts to >> keep/subtract/cancel, it should expand the drawer (for those of us who >> use drawers). > > I've added this to the version of the patch below. > > As another question: > > When attempting to clock into A, and org-resolve-clocks finds a > dangling clock in B, and the user presses "k" or "s" (i.e., not K or > S), do you expect it to clock you into A or into B when the resolution > is done? Right now K will continue the clock-in to A, but k will > abort the clock-in to A and clock you into B to resume that task. Since my intention was to clock in to A, I would find it confusing in any event to suddenly find myself clocked into B. Even in the case of a dangling clock caused by an emacs crash, I would prefer to stay in control! Should task B strike me as the task I would rather be clocking in instead of task A, I would expect to either hit C-g and clock into B, or go through the list of all dangling clocks and come back to B.