From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Kowalczyk Subject: Re: Patch for resolving Date: Fri, 16 Oct 2009 18:13:08 +0000 (UTC) Message-ID: References: <27E1810B-0447-46B3-9AF4-BA14ACECA00A@gmail.com> <23C3964F-E34B-4322-BCC7-3C5F8088CBB3@gmail.com> <8EC805BD-59D2-4549-9A78-E763CDDE1F89@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MyrJB-0003sn-2a for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:13:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyrJ6-0003fa-AC for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:13:44 -0400 Received: from [199.232.76.173] (port=55681 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyrJ6-0003fT-7j for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:13:40 -0400 Received: from lo.gmane.org ([80.91.229.12]:50980) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MyrJ5-0002aE-NZ for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 14:13:40 -0400 Received: from list by lo.gmane.org with local (Exim 4.50) id 1MyrJ2-0001xV-Rd for emacs-orgmode@gnu.org; Fri, 16 Oct 2009 20:13:36 +0200 Received: from 24-216-241-93.dhcp.mdfd.or.charter.com ([24.216.241.93]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Oct 2009 20:13:36 +0200 Received: from jtk by 24-216-241-93.dhcp.mdfd.or.charter.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Oct 2009 20:13:36 +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 gmail.com> writes: > On Oct 16, 2009, at 1:41 PM, John Wiegley wrote: > > > 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? > > I have a better answer for this: > > 1. For the checking idle time, I just check the currently active > clock's file, wherever that happens to be. > > 2. For resolving clocks on clock-in, I'll scan all agenda-files and > open org-mode buffers. > > John Thanks, that plan sounds ideal for the way I use Org, i.e. without the agenda, and one or more open buffers in org-mode for clocking time. I actually haven't gotten around to using the agenda yet, because (and this is purely laziness on this user's part), I never got it to display gridded time for my completed worklogs in the form below (i.e. few things are ahead of time): * Worklog for ACME ** DONE Task 1 :tagA: CLOSED: [2009-10-16 Fri 11:06] :LOGBOOK: CLOCK: [2009-10-16 Fri 09:42]--[2009-10-16 Fri 09:46] => 0:04 :END: Describe. ** DONE Task 2 :tagA:tagB: CLOSED: [2009-10-16 Fri 11:06] :LOGBOOK: CLOCK: [2009-10-16 Fri 10:00]--[2009-10-16 Fri 10:43] => 0:43 CLOCK: [2009-10-16 Fri 09:54]--[2009-10-16 Fri 09:56] => 0:02 :END: Notes taken. ** TODO Task 3 :tagA: :LOGBOOK: CLOCK: [2009-10-16 Fri 11:07] CLOCK: [2009-10-16 Fri 10:43]--[2009-10-16 Fri 10:44] => 0:01 :END: In progress...