From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Wiegley Subject: Re: Re: Patch for resolving "away time" when clocked in Date: Fri, 16 Oct 2009 14:43:24 -0400 Message-ID: <53E5F3F0-6251-4F08-901A-D83AA6A5CD7C@gmail.com> References: <27E1810B-0447-46B3-9AF4-BA14ACECA00A@gmail.com> <877huvmirr.fsf@dynapse.com> <131E75B1-D61D-46B6-A28A-F75F7CFE622E@gmail.com> <87zl7rky7r.fsf@dynapse.com> Mime-Version: 1.0 (Apple Message framework v1075.2) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Myrlz-0008DC-Tv for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:43:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Myrlz-0008Co-Aw for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:43:31 -0400 Received: from [199.232.76.173] (port=48157 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Myrlz-0008Cf-3z for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:43:31 -0400 Received: from fg-out-1718.google.com ([72.14.220.159]:26898) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Myrlx-0007DZ-Uf for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:43:30 -0400 Received: by fg-out-1718.google.com with SMTP id 16so1034816fgg.12 for ; Fri, 16 Oct 2009 11:43:28 -0700 (PDT) In-Reply-To: <87zl7rky7r.fsf@dynapse.com> 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: "Gregory J. Grubbs" Cc: emacs-orgmode@gnu.org On Oct 16, 2009, at 2:09 PM, Gregory J. Grubbs wrote: > 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. Ok, then if the resolution logic is being triggered by a clock-in event, I won't interrupt the user's clock in. In this case both s and S will be equivalent. John