From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?S=C3=A9bastien_Vauban?= Subject: Re: Display missing/overlapping clock ranges Date: Wed, 27 Apr 2011 14:43:26 +0200 Message-ID: <80bozrn9u9.fsf@somewhere.org> References: <87ei56yv2y.fsf@gmail.com> <878vvdj1y6.fsf@norang.ca> <1598DF88-B3E8-4502-956F-3A98113EA5BE@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org 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" a= nd > "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......=20 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......=20 Work: 11:42-12:22 Clocked: (0:40) TODO Organize work 12:00......=20 No end time=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 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 "Ti= me 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 --=20 S=C3=A9bastien Vauban