From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Display missing/overlapping clock ranges
Date: Wed, 27 Apr 2011 14:43:26 +0200 [thread overview]
Message-ID: <80bozrn9u9.fsf@somewhere.org> (raw)
In-Reply-To: 1598DF88-B3E8-4502-956F-3A98113EA5BE@gmail.com
Hi Carsten and all,
Carsten Dominik wrote:
> these are pretty good ideas, and since it is a holiday, I have some time, so
> I have tried an implementation and just pushed it to the master.
>
> This introduces a new key in the agenda, "v c", which will check for
> clocking issues and display them in a similar way as Bernt proposes.
>
> The whole thing works like log view, so it applies to the currently
> displayed span in the agenda, and it sticks if you move around with "f" and
> "b". To get out of this view, press "l" to turn off log view, for example.
>
> Also, it is a special log view in that it only shows clocking information, I
> believe this makes it more direct and useful.
>
> There is a variable to configure what constitutes clocking issues. The
> default value is
>
> (setq org-agenda-clock-consistency-checks
> '(:max-duration "10:00" :min-duration 0 :max-gap "0:05" :gap-ok-around ("4:00")))
>
> which means the following:
>
> 1. Report any clocking chunks that are longer than 10 hours,
> 2. Report clocking chunks that are shorter than 0 minutes
> (so this could be used to find short clocks, by setting it
> to one minute or so)
> 3. Report gaps in the clocking, if the gap is larger than 5 minutes
> (should than be called :min-gap? I am confused....)
First, I would choose "min-gap". But, then, if we look carefully, what you
describe are conditions for being reported:
- max duration allowed; if not, report it
- min duration allowed; if not, report it
- max gap allowed; if not, report it
- ...
So, in this case, "max" makes more sense than "min".
> 4. If the time 4am falls into a large gap, do not report the gap.
> This is to avoid the spurious reporting of gaps between the
> last evening task and the first morning task.
>
> Testing and feedback would be much appreciated.
Great feature! Missed it for long...
> Also, it is not really useful to use this on a filtered agenda view,
> but testing of this would be appreciated as well.
Works perfect.
--8<---------------cut here---------------start------------->8---
2011-04-27 Wed ______________________________________________________
8:00......
Work: 9:08- 9:27 Clocked: (0:19) TODO Organize work
Work: 9:27-11:42 Clocked: (2:15) TODO Read email and news
10:00......
Work: 11:42-12:22 Clocked: (0:40) TODO Organize work
12:00......
No end time
Work: 13:29...... Clocked: (-) TODO Organize work
--8<---------------cut here---------------end--------------->8---
Two remarks:
- I would add another space in front of both strings ("No end time" and "Time
gap"), as they are well highlighted with the fonts customs
- I think I would put "No end time" after the task line, not before.
Thanks a lot!
Best regards,
Seb
--
Sébastien Vauban
next prev parent reply other threads:[~2011-04-27 12:43 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
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 [this message]
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=80bozrn9u9.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).