emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-clock-report to insert a :scope sutree report when called from within a subtree?
Date: Thu, 17 Mar 2011 08:26:43 -0500	[thread overview]
Message-ID: <AANLkTi=tOi2Z20xLd6tyodvWa04OJ4VJwO32qRhYK_C=@mail.gmail.com> (raw)
In-Reply-To: <874o72koig.fsf@altern.org>

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

On Thu, Mar 17, 2011 at 5:52 AM, Bastien <bzg@altern.org> 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 C-r' will insert a clock report with ":scope subtree", and use
> ":scope subtree" elsewhere.
>
> Please let me know if you think that's a bad idea.
>
>
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, I often don't change it again.

Personally, my org-mode usage favors "bite-sized" files that get replaced
over time rather than keeping huge files. My files cover one month and
that's it. Then they are filed away. For me... :scope file isn't a big deal.


John


>
> --
>  Bastien
>
>

[-- Attachment #2: Type: text/html, Size: 1579 bytes --]

  reply	other threads:[~2011-03-17 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 10:52 Bastien
2011-03-17 13:26 ` John Hendy [this message]
2011-03-23 14:16   ` Bastien
2011-03-23 14:12 ` [Accepted] " Bastien Guerry
2011-03-23 14:15 ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=tOi2Z20xLd6tyodvWa04OJ4VJwO32qRhYK_C=@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: org-clock-report to insert a :scope sutree report when called from within a subtree?' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).