unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: John Wiegley <johnw@gnu.org>
Subject: Re: Project/time management for Emacs?
Date: Tue, 10 Dec 2002 13:13:51 -0700	[thread overview]
Message-ID: <87n0ndtyww.fsf@alice.dynodns.net> (raw)
In-Reply-To: 958686cf.0212100907.66392e6f@posting.google.com

>>>>> On Tue Dec 10, Jens writes:

> Hi.  I am looking for a project and time reporting system for
> Emacs.  Basically something in the spirit of timeclock.el, but with
> some more functionality, in particular wrt. reporting ("How much
> time did I spend in the last month on that particular project?").
> It should be simple to use and configure: I just need to check into
> a project, check out of it, and do reporting on the long-term
> results. In particluar, I do not need any planning type of
> functionality.

> I am not sure to what extent timeclock.el has evolved since Emacs
> 21.1, probably it already has the functionality mentioned above ...

> What's your opinion on that?  What would you recommend?

I would recommend using timeclock.el to collect the data you want,
and then writing another utility to make use of it for reporting
purposes.

For example, I have personally written several Perl/Python scripts
to make use of the timeclock.el data that I've gathered over the
years (now 4 years worth).

There is no need for a "do it all" program.  Mixing and matching is
the best way to avoid recoding.  timeclock.el has a simple
interface, and a VERY simple data format.

John

  parent reply	other threads:[~2002-12-10 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <958686cf.0212100907.66392e6f@posting.google.com>
2002-12-10 19:38 ` Project/time management for Emacs? Romain FRANCOISE
2002-12-10 20:13 ` John Wiegley [this message]
2002-12-11  8:59 ` Bernd Wolter

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87n0ndtyww.fsf@alice.dynodns.net \
    --to=johnw@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.
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).