From: Paul Mead <paul.d.mead@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Display missing/overlapping clock ranges
Date: Wed, 13 Apr 2011 17:28:21 +0100 [thread overview]
Message-ID: <87ei56yv2y.fsf@gmail.com> (raw)
In-Reply-To: io4gdf$oq2$1@dough.gmane.org
Rainer Stengele <rainer.stengele@diplan.de> writes:
> Hi all!
>
> I do clock every task I work on during the whole day.
> At the end of the day or week I have to go over all clock entries in my agenda
> and see if there are holes or overlappings in my clock tables.
> If yes I have to adjust the clocks.
>
> I read Bernt Hansen's comments on how he works with clocks
> (http://doc.norang.ca/org-mode.html#Clocking).
>
> What about a function showing the lacking clock ranges over
> the day while being in the agenda with log mode on?
>
> The function could even check for overlapping clock ranges and indicate these
> or jump to these.
>
> Maybe it would even be good to be able to configure daily and weekly
> regular holes in the ranges, for example
>
> - daily lunch time from [12:00]--[13:00]
> - week end days (maybe with diary syntax)
> - working days (Monday to Friday for example)
>
> What do you think?
>
> -- Rainer
I'd defintely use something which identified the gaps and overlaps as
they're taking some time to find now that I have to account more closely
for my time! I've been considering whether to raise this for a
while. The 'regular holes' idea is good to, although not as important
for me.
Paul
next prev parent reply other threads:[~2011-04-13 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 15:44 Display missing/overlapping clock ranges Rainer Stengele
2011-04-13 16:28 ` Paul Mead [this message]
2011-04-13 21:06 ` Bernt Hansen
2011-04-14 8:26 ` Paul Mead
2011-04-14 9:06 ` Rainer Stengele
2011-04-24 15:30 ` Carsten Dominik
2011-04-24 21:48 ` Rainer Stengele
2011-04-24 22:07 ` Carsten Dominik
2011-04-27 11:53 ` Carsten Dominik
2011-05-03 7:05 ` Rainer Stengele
2011-04-24 23:09 ` Bernt Hansen
2011-04-27 12:43 ` Sébastien Vauban
2011-04-19 12:28 ` Rainer Stengele
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=87ei56yv2y.fsf@gmail.com \
--to=paul.d.mead@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).