From: Carsten Dominik <dominik@science.uva.nl>
To: "Jason F. McBrayer" <jmcbray@carcosa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Clocktable from multiple files?
Date: Wed, 19 Sep 2007 21:26:30 +0200 [thread overview]
Message-ID: <df6dbe0e30b0d734b6fa0a0d0f6bcc6d@science.uva.nl> (raw)
In-Reply-To: <m1lkball5e.fsf@bertrand.carcosa.net>
On Sep 13, 2007, at 16:01, Jason F. McBrayer wrote:
> Here are some things that any future org-clock.el or similar ought to
> be able to handle:
>
> 1. Including CLOCK entries from all org-agenda-files in its summaries
This one is really needed, yes. Will add this soon.
> 2. Including CLOCK entries from archive files associated with files
> used
> to construct its summaries. Right now I can't archive completed
> projects because of the need to include them and their tasks in
> monthly reports, for example.
I am not so sure about this. The whole idea about archiving is that
this project should no longer be used in all the list compilation by
org-mode. So my feeling would be that you should keep that tree in
your work file until you no longer need it. Also, with some files
having multiple archive files, this gets messy.
> 3. Conversely, limiting summaries to only a subtree (having a clock
> table per project, for example). I don't need this right now, but
> someone consulting or freelancing for several clients probably
> would.
Indeed, also very useful. This will happen.
- Carsten
next prev parent reply other threads:[~2007-09-19 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 17:02 Clocktable from multiple files? cranreuch
2007-09-13 5:10 ` Carsten Dominik
2007-09-13 14:01 ` Jason F. McBrayer
2007-09-13 15:05 ` Bernt Hansen
2007-09-19 19:28 ` Carsten Dominik
2007-09-13 17:07 ` Bastien
2007-09-19 19:26 ` Carsten Dominik [this message]
2007-09-23 20:26 ` Jason F. McBrayer
2007-09-19 5:39 ` cranreuch
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=df6dbe0e30b0d734b6fa0a0d0f6bcc6d@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=jmcbray@carcosa.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).