From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Clocktable from multiple files?
Date: Thu, 13 Sep 2007 19:07:20 +0200 [thread overview]
Message-ID: <87hclyo5o7.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m1lkball5e.fsf@bertrand.carcosa.net> (Jason F. McBrayer's message of "Thu, 13 Sep 2007 10:01:17 -0400")
jmcbray@carcosa.net (Jason F. McBrayer) writes:
> I can't volunteer to write anything at this point, but I do have some
> comments.
Same here.
> I think accumulating CLOCK entries in the outline is The Right Thing.
I think it's okay, but I guess lots of people (including me) don't care
about the detailed clocking history - I just need to know how much time
I spent on a task.
So a simple :CLOCK: property might be an alternative way to keep track
of all the clocking stuff. We could even refine this and have something
like a :CLOCKED-IN: property for tasks that last more than the duration
of an Emacs session (which equals the lifespan of an Org buffer :)
I would also make it possible to merge all the CLOCK: lines into a
single :CLOCK: property.
Then what we need is to make `org-clock-sum' and `org-clock-display'
handle the new :CLOCK: property so that the :org-clock-minutes property
is uptodate in headlines properties.
For multi-files timeclock reports, I guess collecting :org-clock-minutes
from headlines is the easy way...
> Maybe someone will get inspired by this :)
Sure!
--
Bastien
next prev parent reply other threads:[~2007-09-13 17:07 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 [this message]
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=87hclyo5o7.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).