From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Agenda clock reporting Date: Sun, 03 Jan 2010 10:38:42 -0500 Message-ID: <87aawvi4fx.fsf@gollum.intra.norang.ca> References: <87fx73qhxq.fsf@gollum.intra.norang.ca> <01B0D18A-0F04-44A3-A340-50128FFEFC57@gmail.com> <87eim7i7zd.fsf@gollum.intra.norang.ca> <2728B4EE-06FA-409C-9065-01F388554411@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 1NRSXb-0004BT-94 for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 10:38:51 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NRSXX-00048Z-Hq for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 10:38:50 -0500 Received: from [199.232.76.173] (port=59035 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRSXX-00048P-DD for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 10:38:47 -0500 Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:56981) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NRSXX-0004BH-2E for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 10:38:47 -0500 In-Reply-To: <2728B4EE-06FA-409C-9065-01F388554411@gmail.com> (Carsten Dominik's message of "Sun\, 3 Jan 2010 15\:41\:01 +0100") 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: Carsten Dominik Cc: Carsten Dominik , emacs-orgmode@gnu.org Carsten Dominik writes: > On Jan 3, 2010, at 3:22 PM, Bernt Hansen wrote: > >> Carsten Dominik writes: >> >>> I think the right place would be `org-clock-sum'. Right now, >>> this looks only for complete clock lines. You could modify the >>> regexp >>> to check for incomplete lines (first time stamp only) and then check >>> if the org-clock-marker points to the current line. If yes, you >>> could >>> use the current time as the end time and proceed. >>> >>> Send me a patch if you get this to work, with a customization >>> variable >>> to turn this off. >>> >>> HTH >> >> Yes it does thanks. I found the logic that uses the regexp for >> parsing >> the times and summing them in reverse up to the headline in >> org-clock-sum. I haven't modified the regexp yet but was planning >> something similar to what you describe above. >> >> - org-clock-sum >> - Runs through headings in reverse order >> - counts clock entries bottom up to headline >> - adds a text property to the headline with total time >> - need to find out if current heading is clocking > > Yes, the alternative approach would be to *not* modify the regexp, but > to > check if org-clock-hd-marker points to the current headline and then > add the time since the clock started (in `org-clock-start-time') to > the appropriate > field in the ltimes vector before extracting the total time. So you > would do > this as the first thing when you find a headline, and the proceed > normally. > > Sounds simpler than modifying the regexp and would not cause any > problems > with other incomplete clock entries that may have been left behind and > never > properly resolved...... That does sound simpler ... I'll give that a try. Thanks! Bernt