From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Org clock markers are not consistent with org-clock-history Date: Tue, 23 Apr 2013 14:06:29 -0400 Message-ID: <87k3ntt93u.fsf@norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:60482) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUhc0-0004gm-Cz for emacs-orgmode@gnu.org; Tue, 23 Apr 2013 14:06:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UUhbz-0004z6-1n for emacs-orgmode@gnu.org; Tue, 23 Apr 2013 14:06:40 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:50045) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUhby-0004y7-TT for emacs-orgmode@gnu.org; Tue, 23 Apr 2013 14:06:38 -0400 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org, carsten.dominik@gmail.com Hi Bastien, My workflow has been slightly broken since this commit: ,---- | commit 796b4ec43bef813fc482ca996e8dc2ee3f09200a | Author: Bastien Guerry | Date: Fri Jul 27 17:24:16 2012 +0200 | | org-clock.el: Set the marker for `org-clock-history' at a safer | position. | | * org-clock.el (org-clock-in): Set the marker for | `org-clock-history' at a safer position. | | The clock marker stored in `org-clock-history' used to be at the | beginning of the heading. When manually inserting content here, | the marker is not updated because it is *before* the point. So | set the clock marker right after the first "*" of the headline | so that it will always be correctly updated. `---- This moves the marker for org-clock-history forwards by one character so it's no longer possible to easily check if the org-clock-default-task or org-clock-interrupted-task is the same as the marker in the history list. I have a function bound to F9-SPC which skips back to the previously clocked task and it used to skip over the default task ... but this no longer works because the marker in history no longer matches the default task. This has been broken for a long time (since July) but I just now spent the time to figure out exactly why. The markers and history used to be consistent and this is no longer the case. Can the other markers also be moved forward one char to match the history marker or do I need to modify my function to compute a new marker so I can compare it with what is in the clock history? Shouldn't ALL clock markers be treated the same way? (Either move them all forward or none of them) Thanks, Bernt