From: Matthew Lundin <email@example.com>
To: Peter Jones <firstname.lastname@example.org>
Subject: Re: Re: time tracking common activities
Date: Fri, 20 Feb 2009 10:01:48 -0600 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Peter Jones's message of "Fri, 20 Feb 2009 08:45:40 -0700")
Peter Jones <email@example.com> writes:
> David Bremner <firstname.lastname@example.org> 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
>> I guess you would still have to think about comfortable ways to find
>> the right file/buffer and clock in there.
> I think this is probably the key to making this successful. If it takes
> you too long to locate the headings, you won't bother clocking in.
> What's the best way to quickly get to a heading?
The easiest way to do this is via the agenda. Simply type "I" and you
will clock into the task. Type "X" to clock out. If you set the variable
org-clock-in-switch-to-state you can automatically clock in when
switching to a particular todo.
> What are other people doing to quickly get to a specific heading?
Again, the agenda and org-follow is the easiest way to get to headings.
next prev parent reply other threads:[~2009-02-20 16:00 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
2009-02-20 15:49 ` Bernt Hansen
2009-02-20 15:45 ` Peter Jones
2009-02-20 16:01 ` Matthew Lundin [this message]
2009-02-20 20:30 ` Sebastian Rose
2009-02-21 3:51 ` J Aaron Farr
2009-02-20 14:40 ` Jason F. McBrayer
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 \
* 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).