emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Olaf Dietsche <olaf+list.orgmode@olafdietsche.de>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Overall organization/setup for org mode: Projects and Tasks
Date: Wed, 14 Sep 2011 23:04:07 +0200	[thread overview]
Message-ID: <4E7116C7.4040605@christianmoe.com> (raw)
In-Reply-To: <87fwjzar2j.fsf@rat.lan>

I realize that other people's mileage may and does differ, but 
personally, I have long found the amazing functionality, 
customizability and hackability of Org-mode an astonishingly effective 
tool for PTO (Putting Things Off).



On 9/14/11 8:59 PM, Olaf Dietsche wrote:
> Hi Alan,
> "Alan E. Davis"<lngndvs@gmail.com>  writes:
>> I've been using org-mode for a few years.  My agenda is cluttered with tasks
>> that are weeks and even months past due.  I am "this close" to declaring
>> "orgmode bankruptcy" and starting from scratch, except my current setup
>> works so well for other things.   Might still do that, but I want to ask for
>> ideas.
> I (and many others) struggle too with becoming "organized". And usually
> it's not a "tool bankruptcy", but the lack of a coherent system.
> What helped me to some degree - and I'm still learning - was David
> Allen's book "Getting Things DONE". You will find lots of information
> about GTD in the internet (google, youtube) and at the orgmode website
> <http://orgmode.org/worg/org-gtd-etc.html>. I also took lots of good
> ideas and .emacs snippets from Bernt Hansen's website at:
> <http://doc.norang.ca/org-mode.html>.
> And although GTD is a pretty simple system once you get it, I suggest,
> take the time and read the book (your library might have a copy) and
> start slowly from there on.
>> I stumble consistently over the distinction between projects and tasks.  I
>> think there is not clear distinction, but I need to find a way to organize
>> them so that, at least, agenda displays the day to day TODO tasks separated
>> in a meaningful way from the long term projects that I need to remind myself
>> of (and there are dozens of these).
> Both projects and tasks result in actions, which have to be completed
> eventually. So there's not really any difference in handling these,
> besides maybe the number of single steps it takes to complete.
> And finally, paraphrasing Pete Phillips in
> <http://article.gmane.org/gmane.emacs.orgmode/4854>, there will be the
> time, where you have to bite the bullet and "just do it".
> Regards, Olaf

  reply	other threads:[~2011-09-14 21:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14 17:43 Alan E. Davis
2011-09-14 18:26 ` Thomas S. Dye
2011-09-14 18:40 ` Russell Adams
2011-09-14 20:00   ` Martyn Jago
2011-09-14 22:50     ` Russell Adams
2011-09-14 18:59 ` Olaf Dietsche
2011-09-14 21:04   ` Christian Moe [this message]
2011-09-14 21:49   ` Darlan Cavalcante Moreira
2011-09-17 19:32 ` Max Mikhanosha
2011-09-18 19:22   ` Alan E. Davis
2011-09-18  2:40 ` David Rogers

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=4E7116C7.4040605@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=olaf+list.orgmode@olafdietsche.de \


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