From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: [PATCH] * doc/org.texi (Agenda commands): Document org-clock-report-include-clocking-task Date: Wed, 04 Jan 2012 07:13:04 -0500 Message-ID: <87pqez4qen.fsf@norang.ca> References: <3CF43367-3C9C-4509-8383-90A26C016D2A@gmail.com> <1323886204-17875-1-git-send-email-bernt@norang.ca> <87hb136mvk.fsf@gnu.org> <80vcosqxsf.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:41828) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiPib-0006Ee-Nr for emacs-orgmode@gnu.org; Wed, 04 Jan 2012 07:13:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RiPia-0007kE-72 for emacs-orgmode@gnu.org; Wed, 04 Jan 2012 07:13:21 -0500 Received: from plane.gmane.org ([80.91.229.3]:58089) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiPiZ-0007kA-Up for emacs-orgmode@gnu.org; Wed, 04 Jan 2012 07:13:20 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1RiPiU-0001MN-PN for emacs-orgmode@gnu.org; Wed, 04 Jan 2012 13:13:14 +0100 In-Reply-To: <80vcosqxsf.fsf@somewhere.org> (Sebastien Vauban's message of "Tue, 03 Jan 2012 22:30:24 +0100") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org "Sebastien Vauban" writes: > Hi Bastien, > > Bastien wrote: >> Bernt Hansen writes: >> >>> Add reference to this variable when describing the agenda clock >>> report. >> >> Applied, thanks. >> >>> Here's the documentation patch. I won't be offended if you decide not >>> to apply it since we don't document every customizable variable in >>> org-mode. >> >> I think this one is important. > > This one appears important because its default value is not set as one would > or could expect. Shouldn't we set it to `t' by default? The default value was set as is so that behaviour didn't change before this variable and related code was introduced. The clock reports never used to consider the current clocking item before this patch went in. It may very well make more sense to turn it on by default. Regards, Bernt