From: jmcbray@carcosa.net (Jason F. McBrayer)
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Clocktable from multiple files?
Date: Thu, 13 Sep 2007 10:01:17 -0400 [thread overview]
Message-ID: <m1lkball5e.fsf@bertrand.carcosa.net> (raw)
In-Reply-To: <05bd06e8cce5d8c8ccdddeebf980da98@science.uva.nl> (Carsten Dominik's message of "Thu, 13 Sep 2007 07:10:36 +0200")
Carsten Dominik <dominik@science.uva.nl> writes:
> In fact, maybe the whole clocking stuff needs an overhaul at some
> point, but right now I don't have time to do it. I not sure in what
> direction to take this. Maybe create a timeclock - compatible list
> from scanning the agenda buffers? I still think that collecting the
> CLOCK entries in the outline does make a lot of sense. The clock
> table was a quick hack I once did, but apparently not really though
> through very well.
I can't volunteer to write anything at this point, but I do have some
comments.
I think accumulating CLOCK entries in the outline is The Right Thing.
It keeps the times with the tasks, and so forth, and clocking in and out
of tasks is really convenient. What we're lacking right now are
flexible-enough ways of dealing with the information those entries
represent. Right now, the clock table does everything I really need to
do, but not everything I would like to be able to do.
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
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.
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.
Maybe someone will get inspired by this :)
--
+-----------------------------------------------------------+
| Jason F. McBrayer jmcbray@carcosa.net |
| If someone conquers a thousand times a thousand others in |
| battle, and someone else conquers himself, the latter one |
| is the greatest of all conquerors. --- The Dhammapada |
next prev parent reply other threads:[~2007-09-13 14:01 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 [this message]
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
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=m1lkball5e.fsf@bertrand.carcosa.net \
--to=jmcbray@carcosa.net \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
/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).