From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben McGinnes Subject: Bug or known issue: org-clock-display Date: Tue, 15 Jan 2019 03:07:37 +1100 Message-ID: <20190114160737.5z7vzilh3bgkkq5e@adversary.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dygcfnovhn6f3hyr" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:54768) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gj4tm-00074l-PJ for emacs-orgmode@gnu.org; Mon, 14 Jan 2019 11:15:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gj4tm-00068F-2B for emacs-orgmode@gnu.org; Mon, 14 Jan 2019 11:15:38 -0500 Received: from ec2-52-29-175-128.eu-central-1.compute.amazonaws.com ([52.29.175.128]:10938 helo=devious.adversary.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gj4tl-00063F-Qy for emacs-orgmode@gnu.org; Mon, 14 Jan 2019 11:15:37 -0500 Received: from adversary.org (localhost [127.0.0.1]) by devious.adversary.org (Postfix) with ESMTP id 8BC9848468 for ; Mon, 14 Jan 2019 16:07:57 +0000 (UTC) Content-Disposition: inline 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" To: emacs-orgmode@gnu.org --dygcfnovhn6f3hyr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, I've been using org-mode to perform the task of timesheets with another GNU project and encountered something which has all the hallmarks of a bug. I'm just not sure if it's a known issue or whether to write up a bug report for it. I use org-clock-in and org-clock-out to track the hours worked and then at the end of each month use org-clock-display to obtain the total hours to bill for. This was going fine all year until January 1st. At this point I can no longer see the totals and org-clock-display produces the following error message: Total file time: 0:00 (0 hours and 0 minutes) If I do a find and replace of 2018 to 2019, however, the correct calculations occur as expected. So it appears that org-clock-display only works for the year you're in. BTW, the test I performed on just December, the correct total time message is: Total file time: 5d 22:39 (142 hours and 39 minutes) A bit of a difference. ;) So, is this a known issue with possibly some arcane reason for why it can't easily be fixed or is my next step to go lodge a formal bug report? Regards, Ben --dygcfnovhn6f3hyr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABEKAB0WIQSkiyjzmoPmPFW48w5Icjp1eQQexgUCXDyzyQAKCRBIcjp1eQQe xvmYAPsH+w7a6/QUgfmcQHRTM1Bj9qntnxcfHWwulVvReZWL/gEAgDqWV5B3be/6 nQHGNvdjh2QVc7VVe7BKAJNS2KJGSrE= =6nlX -----END PGP SIGNATURE----- --dygcfnovhn6f3hyr--