From: Bernt Hansen <bernt@norang.ca>
To: Bastien <bastienguerry@googlemail.com>
Cc: emacs-orgmode@gnu.org, carsten.dominik@gmail.com
Subject: Org clock markers are not consistent with org-clock-history
Date: Tue, 23 Apr 2013 14:06:29 -0400 [thread overview]
Message-ID: <87k3ntt93u.fsf@norang.ca> (raw)
Hi Bastien,
My workflow has been slightly broken since this commit:
,----
| commit 796b4ec43bef813fc482ca996e8dc2ee3f09200a
| Author: Bastien Guerry <bzg@altern.org>
| 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
next reply other threads:[~2013-04-23 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 18:06 Bernt Hansen [this message]
2013-04-24 8:48 ` Bastien
2013-04-24 14:19 ` Bernt Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3ntt93u.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=bastienguerry@googlemail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--subject='Re: Org clock markers are not consistent with org-clock-history' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).