emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Memnon Anon <gegendosenfleisch@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Organize Your Life In Plain Text!
Date: Thu, 07 May 2009 18:32:14 -0400	[thread overview]
Message-ID: <87bpq4v91t.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <4a035da6.0407560a.7391.ffffc270@mx.google.com> (Memnon Anon's message of "Fri\, 08 May 2009 00\:15\:49 +0200")

cc-ing the org-mode mailing list

Memnon Anon <gegendosenfleisch@googlemail.com> writes:

> Hi!
>
> I have one question:
>
> ,----
> | Use the agenda view for STARTED tasks to find stuff in progress and
> | things to clock. I clock everything - some tasks are always in a STARTED
> | state (Like Organization, Email News and IRC, etc)
> `----
>
> Doesn't it defeat the purpose to a certain degree to keep tasks
> 'started' all the time? I intend to increase my personal logging, 
> but I think I will keep some tasks like 'mail+news' without any
> todo state. Maybe an extra state -'undefined' or 'rep' or something like
> this- for this kind would be clever? 
>
> What do you think?
>  

Hi!

I used to have a special keyword ONGOING for things that I do a lot and
want to clock but never really start/end.  I had a special agenda view
for ONGOING tasks that I would pull up to easily find the thing I want
to clock.

Since then I've moved away from using the ONGOING todo keyword and just
use STARTED the same way.  If a task is clocked in it automatically
moves to a STARTED todo state and shows up on the list without having to
think about it.  Having an agenda view that shows STARTED tasks makes it
easy to pick the thing to clock - and I don't have to remember if I need
to look in the ONGOING list or the STARTED list when looking for the
task to clock in.  The STARTED list is basically 'what is current' -
stuff I worked on recently and need to continue working on.  I want to
find the thing to work on as fast as I can and actually do work on it -
not spend time hunting through my org files for the task that needs to
be clocked in.

I just find it easier to have it all in one short list.  My STARTED list
has less than 20 entries so it's pretty easy to find what I want.  The
whole point of the STARTED list is to make it easy and quick to find the
task to clock in.

I only have 2 tasks that are permanently in a STARTED state.  These are:

  - Organization
  - Email, News, and IRC

Everything else will eventually move to a DONE state and fall off the
list.

I found having two lists more confusing than just the single STARTED
list.

-Bernt

  parent reply	other threads:[~2009-05-07 22:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 16:49 Organize Your Life In Plain Text! Bernt Hansen
2009-05-07 18:22 ` Rick Moynihan
2009-05-07 18:44   ` Bernt Hansen
     [not found]     ` <4a035da6.0407560a.7391.ffffc270@mx.google.com>
2009-05-07 22:32       ` Bernt Hansen [this message]
2009-05-08  2:10         ` Memnon Anon
2009-05-08  3:04           ` Bernt Hansen
2009-05-07 22:50     ` Jonathan Arkell
2009-05-08  1:35       ` Rick Moynihan
2009-05-08  1:46         ` Eric Schulte
2009-05-08 14:08           ` Carsten Dominik
2009-05-08 15:32             ` Eric Schulte
2009-05-08 16:19               ` Carsten Dominik
2009-05-13  0:22 ` Rick Moynihan
2009-05-13  1:39   ` Bernt Hansen
2009-05-13  1:50   ` Bernt Hansen
2009-05-13  3:58     ` Carsten Dominik
2009-05-13  4:02       ` Bernt Hansen
2009-05-13 10:04         ` Sebastian Rose
2009-05-13 10:15           ` Rick Moynihan
2009-05-14 13:33             ` Eric Schulte
2009-05-14 19:30               ` Sebastian Rose
2009-05-14 19:55                 ` Keith Lancaster
2009-05-14 22:16                   ` Eric Schulte
2009-05-15  6:54                     ` Ian Barton
2009-05-15 22:18                       ` Eric Schulte
2009-05-16  6:56                         ` Ian Barton
2009-05-17 21:49                           ` Eric Schulte
2009-05-18  6:06                             ` Ian Barton
2009-05-18 13:17                               ` Eric Schulte
2009-05-19  9:19                                 ` Ian Barton
2009-05-14 11:36           ` Carsten Dominik
2009-05-14 19:11             ` Bernt Hansen

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=87bpq4v91t.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=gegendosenfleisch@googlemail.com \
    /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).