From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Borkowski Subject: Why is ":CLOCK => hh:mm" allowed as a clock entry? Date: Thu, 18 Oct 2018 09:33:09 +0200 Message-ID: <87ftx3wvyi.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41174) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gD2pp-0005lX-5b for emacs-orgmode@gnu.org; Thu, 18 Oct 2018 03:35:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gD2pl-0002af-5p for emacs-orgmode@gnu.org; Thu, 18 Oct 2018 03:35:09 -0400 Received: from mail.mojserwer.eu ([195.110.48.8]:55396) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gD2pk-0002Tf-SM for emacs-orgmode@gnu.org; Thu, 18 Oct 2018 03:35:05 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id C5B40E683A for ; Thu, 18 Oct 2018 09:35:01 +0200 (CEST) Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YeNqnbBZ6Y9F for ; Thu, 18 Oct 2018 09:34:56 +0200 (CEST) Received: from localhost (83.25.113.210.ipv4.supernova.orange.pl [83.25.113.210]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 63EFEE6257 for ; Thu, 18 Oct 2018 09:34:56 +0200 (CEST) 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: Org-Mode mailing list Hi all, I am studying the `org-clock-sum' function (I need to parse an Org file and extract clocking data), and I noticed that ":CLOCK => hh:mm" is allowed as a clock entry. The Org syntax at https://orgmode.org/worg/dev/org-syntax.html#Clock,_Diary_Sexp_and_Planning confirms this. What is the rationale behind this? I want not only to sum the clocks (org-clock-sum does that, of course), but I want more detailed information (like how many clocks were that in the given period etc.). The format with only the duration makes this troublesome, and I'd like to ignore such entries (I have never seen them in my files, of course). I'm wondering what scenario could lead to their existence? BTW, the syntax draft says that there can be any TIMESTAMP object before the DURATION, but `org-clock-sum' assumes that its timestamps are inactive. Isn't that a bug? TIA, -- Marcin Borkowski http://mbork.pl