Hello,
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
'done))))
(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
'done))))
(todo "WAIT" ((org-agenda-sorting-strategy '(priority-down))
(org-agenda-overriding-header "Waiting For")))
(todo "NEXT" ((org-agenda-sorting-strategy '(priority-down effort-
down))
(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-
down))
(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))))
and
'(org-enforce-todo-checkbox-dependencies t)
'(org-enforce-todo-dependencies t)
this works really well for GTD.
Kind regards,
Daniel
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.
