emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Bausch <DanielBausch@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: What do you use to identify projects (in the GTD sense)
Date: Mon, 10 Oct 2011 13:30:44 +0200	[thread overview]
Message-ID: <201110101330.44437.DanielBausch@gmx.de> (raw)
In-Reply-To: <CACHMzOHa8=ehOA3y+0kmJHVcfi0oN-RbC1_BObGXRaJoCG_sWg@mail.gmail.com>


I use a todo keyword "PROJ" and a custom block agenda, that filters different 
interesting groups for review.

(setq org-agenda-custom-commands
      '(("g" "My GTD Agenda"
         ((agenda "" ((org-agenda-ndays 1)
                      (org-agenda-start-on-weekday nil)
                      (org-agenda-entry-types '(:timestamp :sexp))
                      (org-agenda-overriding-header "Appointments")))
          (agenda "" ((org-agenda-ndays 1)
                      (org-agenda-start-on-weekday nil)
                      (org-agenda-entry-types '(:deadline))
                      (org-agenda-overriding-header "Upcoming Deadlines")
                      (org-agenda-sorting-strategy '(priority-down time-down))
		      (org-agenda-skip-function '(org-agenda-skip-entry-if 'todo 
          (agenda "" ((org-agenda-ndays 1)
                      (org-agenda-start-on-weekday nil)
                      (org-agenda-entry-types '(:scheduled))
                      (org-agenda-overriding-header "Scheduled")
                      (org-agenda-sorting-strategy '(priority-down time-down))
		      (org-agenda-skip-function '(org-agenda-skip-entry-if 'todo 
          (todo "WAIT" ((org-agenda-sorting-strategy '(priority-down))
                        (org-agenda-overriding-header "Waiting For")))
          (todo "NEXT" ((org-agenda-sorting-strategy '(priority-down effort-
                        (org-agenda-skip-function '(org-agenda-skip-entry-if 
'scheduled 'deadline))
                        (org-agenda-overriding-header "Next actions not being 
scheduled nor having a deadline")))
          (todo "TODO" ((org-agenda-sorting-strategy '(priority-down effort-
                        (org-agenda-skip-function '(org-agenda-skip-entry-if 
'scheduled 'deadline))
                        (org-agenda-overriding-header "Future actions not 
being scheduled nor having a deadline")))
          (todo "PROJ" ((org-agenda-overriding-header "Active Projects")))))))

Along with colors

 '(org-todo-keyword-faces (quote (("PROJ" :foreground "Orange" :weight bold) 
("MSTN" :foreground "VioletRed" :weight bold) ("WAIT" :foreground "Blue" 
:weight bold) ("CNCL" :foreground "MediumSeaGreen" :weight bold))))


 '(org-enforce-todo-checkbox-dependencies t)
 '(org-enforce-todo-dependencies t)

this works really well for GTD.

Kind regards, 

Am Montag 10 Oktober 2011, 08:21:57 schrieb Marcelo de Moraes Serpa:
> Hey list,
> I'm wondering if you make the distinction between projects and actionable
> items. If you stop to think about it (specially if you read GTD by David
> Allen), you see that you can't really "do" a project, but only actions
> related to it. It's a powerful and underestimated concept. Of course, a
> todo list is still a reminder of things, and any list can be useful, but
> the more specific you are, the less you have to think (process) and the
> more you can actually execute.
> Anyway, I was wondering how you guys differentiate between projects and
> next actions (todo's) in your org lists. I myself use a :project: tag for
> projects and todos have todo keywords before them. Projects never have a
> todo keyword, except when DONE. I used to use a PROJECT keyword before,
> but I felt that a tag seems to work better (and allows you to actually
> filter todos without mixing projects). So, a typical list looks like this:
> * New feature :project:
> ** TODO Create a mockup for the index page
> ** TODO Convert the mockup to html
> * Renew passport :project:
> ** DONE Call for appointment
> ** TODO Interveiw
>     SCHEDULED <...>
> ** DONE Buy groceries :project: ...
> How do you do it?
> Thanks in advance,
> - Marcelo.

  reply	other threads:[~2011-10-10 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10  6:21 What do you use to identify projects (in the GTD sense) Marcelo de Moraes Serpa
2011-10-10 11:30 ` Daniel Bausch [this message]
2011-10-10 18:44   ` Marcelo de Moraes Serpa
2011-10-11  6:20     ` Daniel Bausch
2011-10-11  1:28 ` Bernt Hansen
2011-10-11  8:16   ` Sven Bretfeld
2011-12-11 16:49   ` Viktor Rosenfeld
2011-12-11 22:18     ` Bernt Hansen
2011-12-12 18:29       ` Viktor Rosenfeld
2011-12-12 19:58         ` Bernt Hansen
2011-12-15 14:41         ` Defining dependencies (was: What do you use to identify projects (in the GTD sense)) Karl Voit

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=201110101330.44437.DanielBausch@gmx.de \
    --to=danielbausch@gmx.de \
    --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).