Bastien writes:
> The default when creating a clock report is to use :scope file. I find
> it not practical for big files, where the report can take long to build.
>
> I'm thinking of applying this change: when called from within a subtree,
> `C-c C-x C-r' will insert a clock report with ":scope
harset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] org-clock-report to insert a :scope sutree report when called
> from within a subtree?
> Date: Thu, 17 Mar 2011 15:52:23 -
> From: Bastien Guerry
> X-Patchwork-Id: 696
> Mess
Hi John,
John Hendy writes:
> It probably depends on the number of people using huge files vs.
> those not. Or the number of people who want this vs. those that
> don't. Actually, I don't think it really matters because it's so easy
> to change it anyway. Once it's created and changed a little,
On Thu, Mar 17, 2011 at 5:52 AM, Bastien wrote:
> Hi all,
>
> The default when creating a clock report is to use :scope file. I find
> it not practical for big files, where the report can take long to build.
>
> I'm thinking of applying this change: when called from within a subtree,
> `C-c C-x
Hi all,
The default when creating a clock report is to use :scope file. I find
it not practical for big files, where the report can take long to build.
I'm thinking of applying this change: when called from within a subtree,
`C-c C-x C-r' will insert a clock report with ":scope subtree", and use
