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 13:41:27 -0400 Message-ID: References: <27E1810B-0447-46B3-9AF4-BA14ACECA00A@gmail.com> <23C3964F-E34B-4322-BCC7-3C5F8088CBB3@gmail.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 1Myqo4-0007kr-MA for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 13:41:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Myqo0-0007hn-2A for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 13:41:36 -0400 Received: from [199.232.76.173] (port=45406 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Myqnz-0007hd-TR for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 13:41:31 -0400 Received: from mail-fx0-f228.google.com ([209.85.220.228]:44227) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Myqnz-0005tU-HS for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 13:41:31 -0400 Received: by fxm28 with SMTP id 28so2672454fxm.42 for ; Fri, 16 Oct 2009 10:41:30 -0700 (PDT) In-Reply-To: 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: Jeff Kowalczyk Cc: emacs-orgmode@gnu.org On Oct 16, 2009, at 1:02 PM, Jeff Kowalczyk wrote: >> I am unable to reproduce the >> cancel-timer failure here. Please load org-clock.el into Emacs and >> type M-x eval-buffer and then trigger it again, that I may see the >> complete stack trace. > > No error anymore as mentioned above. > > I'm not sure I'm triggering the new functionality correctly. In the > scratch > buffer, I eval'd: > > (setq org-clock-idle-time 1) Ah, I think I see where the cancel-timer bug came from. You had set org-clock-idle-timer to 1, rather than org-clock-idle-time (only the latter is a user-customizable variable). > Next, I created an Org buffer with one TODO file, and clocked in, > and took my > hands off the computer. I waited three minutes, then clocked out. > > * Worklog > ** TODO Task 1 > :LOGBOOK: > CLOCK: [2009-10-16 Fri 09:42]--[2009-10-16 Fri 09:46] => 0:04 > :END: > > Was I supposed to be prompted to resolve some minutes when clocking > out after > the org-clock-idle-time had elapsed? At the moment, the auto-resolver only checks files which are referred to by org-agenda-files. It does not scan the entire buffer list looking for any org-mode buffer. Do you think it should do the latter instead? John