From: Bernt Hansen <bernt@alumni.uwaterloo.ca>
To: David O'Toole <dto@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: another GTD question from dto
Date: Wed, 03 Oct 2007 11:33:26 -0400 [thread overview]
Message-ID: <87y7ekb4c9.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <m3hcl8s2xi.fsf@gnu.org> (David O'Toole's message of "Wed\, 03 Oct 2007 10\:11\:53 -0400")
David O'Toole <dto@gnu.org> writes:
> I've been in my new "simple GTD" system for about a week, and it feels
> very comfortable. Thanks again to Carsten and to the org-mode
> community.
>
> Now I see what was wrong with my previous uses of org-mode. I never
> used any keywords other than TODO and DONE. This didn't give enough
> information, so it meant that every task I might possibly ever do had
> a TODO item. Because of the absurd number of TODO's I never used the
> agenda feature much, and therefore didn't schedule many things; I
> relied on my cell-phone for scheduling appointments, and never set
> deadlines in my personal coding projects.
>
> Now I am scheduling more things, and using the agenda views
> regularly.
>
> But I am still having one problem. Right now I have a section in my
> One Big Orgfile that looks like this:
>
>> * Books
>> ** TODO Read "Tractatus Logico-Philosophicus"
>> *** DONE Find out about Wittgenstein's notation
>> *** NEXT Chapter 5
>> *** TODO Chapter 6
>> *** TODO Chapter 7
>> *** TODO Review entire book
>> *** MAYBE [[http://s22318.tsbvi.edu/mathproject/appB-sec1.asp][Spoken mathematics]]
>> ** TODO Read "The Analysis of Mind"
>> *** NEXT Chapter 1
>
> This gives in the agenda:
>
> dto: Scheduled: NEXT Chapter 5
> dto: Scheduled: NEXT Chapter 1
>
> Without any indication which book the chapters are from. Can I fix
> this with properties or tags or categories or something?
I'm less than a week into my shiny new GTD setup.
I don't normally schedule tasks that don't need to be scheduled anymore.
I spend more time "doing stuff" than rescheduling things. I have a
PROJECT and PROJDONE task which I use only for project headlines - and
the PROJECT task defines what is a project. I schedule some of the
important PROJECT tasks (not their subtasks) just to keep them on my
radar in the daily agenda view.
My NEXT tag view for @home is @home/NEXT|PROJECT so my view is something
like this:
todo: .PROJECT Learn Ruby on Rails - Agile Development on Rails Depot Application tutorial
todo: ...NEXT Chapter 6 :sub60:
which shows the book title. You can also use follow mode in the agenda
if you reveal the parent headings with org-show-hierarchy-above t.
I don't know of a way to see it directly in the agenda if you only
display the NEXT task.
HTH,
Bernt
next prev parent reply other threads:[~2007-10-03 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 14:11 another GTD question from dto David O'Toole
2007-10-03 15:33 ` Bernt Hansen [this message]
2007-10-03 20:55 ` Bastien
2007-10-06 23:23 ` Jason F. McBrayer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y7ekb4c9.fsf@gollum.intra.norang.ca \
--to=bernt@alumni.uwaterloo.ca \
--cc=dto@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.