emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: David Bremner <bremner@unb.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: time tracking common activities
Date: Fri, 20 Feb 2009 10:01:54 -0500	[thread overview]
Message-ID: <87ljs1ywwt.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87skm9p9qj.wl%bremner@pivot.cs.unb.ca> (David Bremner's message of "Fri\, 20 Feb 2009 08\:35\:00 -0400")

David Bremner <bremner@unb.ca> writes:

> J Aaron Farr wrote:
>>I'm using org-mode to track my time on projects and todo items, but
>>I'd also like to start tracking time I spend on things such as my
>>email, reading rss feeds, etc.  I'd prefer to continue to use
>>org-mode for that so that all my time tracking is in one place with
>>one system.
>>My current thought is to have a `diary.org` file that I keep tasks
>>that don't clearly fit in any of my projects.  The file would look
>>something like:
>>    *** DONE Checking email                  :email:
>>        CLOSED: [2009-02-20 Fri 18:56]
>>        :CLOCK:
>>        CLOCK: [2009-02-20 Fri 17:56]--[2009-02-20 Fri 18:56] =>  1:00
>>        :END:
> I don't see anything wrong with this, but I also don't see the need
> for a TODO. Do you need to be reminded to check email?  You could just
> make a headline, and clock on that.  Clocktables (or, maybe,
> clocktable view in agenda mode) could narrow down e.g. time spent
> reading email in one week.
> I guess you would still have to think about comfortable ways to find
> the right file/buffer and clock in there.

When I did something similar to this recently I created a tag for
:ONGOING: tasks and used the agenda view to quickly find these tasks for
clocking in.

I just used a single task to clock multiple times and then at the end of
the year create a new one and archive the old one so they don't grow


  reply	other threads:[~2009-02-20 15:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 12:20 time tracking common activities J Aaron Farr
2009-02-20 12:35 ` David Bremner
2009-02-20 15:01   ` Bernt Hansen [this message]
2009-02-20 15:49     ` Bernt Hansen
2009-02-20 15:45   ` Peter Jones
2009-02-20 16:01     ` Matthew Lundin
2009-02-20 20:30       ` Sebastian Rose
2009-02-21  3:51       ` J Aaron Farr
2009-02-20 14:40 ` Jason F. McBrayer

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:

  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=87ljs1ywwt.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=bremner@unb.ca \
    --cc=emacs-orgmode@gnu.org \


* 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


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).