From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Regression? Clocktable no longer includes TODO keywords
Date: Wed, 12 Jul 2017 14:08:40 +0200
Message-ID: <87mv8926yf.fsf@nicolasgoaziou.fr>
References: <87bmopdg6m.fsf@jaunder.io>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57398)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1dVGRh-0006Bt-QG
	for emacs-orgmode@gnu.org; Wed, 12 Jul 2017 08:08:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1dVGRg-00076y-Sb
	for emacs-orgmode@gnu.org; Wed, 12 Jul 2017 08:08:45 -0400
Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:46188)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mail@nicolasgoaziou.fr>)
	id 1dVGRg-00075h-Lg
	for emacs-orgmode@gnu.org; Wed, 12 Jul 2017 08:08:44 -0400
In-Reply-To: <87bmopdg6m.fsf@jaunder.io> (Michael Alan Dorman's message of
	"Wed, 12 Jul 2017 07:53:53 -0400")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Michael Alan Dorman <mdorman@jaunder.io>
Cc: emacs-orgmode@gnu.org

Hello,

Michael Alan Dorman <mdorman@jaunder.io> writes:

> Given the following document:
>
>     * TODO Thingy
>     ** TODO Sub-Thingy 1
>        :LOGBOOK:
>        CLOCK: [2017-07-12 Wed 07:15]--[2017-07-12 Wed 07:25] =>  0:10
>        :END:
>     ** DONE Sub-Thingy 2
>        :LOGBOOK:
>        CLOCK: [2017-07-12 Wed 07:25]--[2017-07-12 Wed 07:31] =>  0:06
>        :END:
>
> I would previously get a clocktable like (simulated):
>
>     #+BEGIN: clocktable
>     #+CAPTION: Clock summary at [2017-07-12 Wed 07:32]
>
>     | Headline              | Time   |      |
>     |-----------------------+--------+------|
>     | *Total time*          | *0:16* |      |
>     |-----------------------+--------+------|
>     | TODO Thingy           | 0:16   |      |
>     | \_  TODO Sub-Thingy 1 |        | 0:10 |
>     | \_  DONE Sub-Thingy 2 |        | 0:06 |
>     #+END:
>
> Starting with (I believe) org 9.05, I get
>
>     #+BEGIN: clocktable
>     #+CAPTION: Clock summary at [2017-07-12 Wed 07:32]
>
>     | Headline         | Time   |      |
>     |------------------+--------+------|
>     | *Total time*     | *0:16* |      |
>     |------------------+--------+------|
>     | Thingy           | 0:16   |      |
>     | \_  Sub-Thingy 1 |        | 0:10 |
>     | \_  Sub-Thingy 2 |        | 0:06 |
>     #+END:
>
> I don't see any note of this in ORG-NEWS, so I assume it's a
> regression.  I haven't had a chance to really dig into it yet.

This doesn't ring a bell. Anyway, the current behaviour sounds right,
since you can get TODO state with the "TODO" special property anyway.

Regards,

-- 
Nicolas Goaziou