From: Bernt Hansen <bernt@norang.ca>
To: Chris Barber <c.barber80@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-for GTD: Some implementation questions
Date: Fri, 21 Jan 2011 20:27:39 -0500 [thread overview]
Message-ID: <8739ol7mno.fsf@norang.ca> (raw)
In-Reply-To: <4D3A0693.1010502@gmail.com> (Chris Barber's message of "Sat, 22 Jan 2011 09:20:03 +1100")
Hi Chris,
Comments are inline below:
Chris Barber <c.barber80@gmail.com> writes:
> Hi, I am currently using Org-mode to apply GTD
> I was wondering what you would do with the following situations:
> My todo sequence is next -> done, and someday, delegate -> waiting,
> cancelled
I would also add a TODO state - not everything is NEXT or WAITING is it?
#+TODO: TODO(t) NEXT(n) | DONE(d)
#+TODO: SOMEDAY(s) DELEGATE(D) WAITING(w) | CANCELLED(c)
> - For scheduled tasks, would you make these tasks NEXTs or would you
> set them as waiting? If NEXTs, how would you filter the agenda to not
> show these scheduled NEXTs?
I just make scheduled tasks TODO to keep them off my NEXT lists. I also
set org-todo-ignore-scheduled as follows so these tasks don't show up in
my global todo lists before I plan to work on them.
#+begin_src emacs-lisp
(setq org-todo-ignore-scheduled 'future
#+end_src
> - For a heading with three subtasks, if the last 2 subtasks require
> the first subtask to be completed, how would you handle this?
I'm assuming you have to do subtask 1 first, and then subtasks 2 and 3
can be done in any order after task one. This seems to work:
* TODO Project
:PROPERTIES:
:ORDERED: t
:END:
** TODO Step 1
** TODO Step 2 and 3
*** TODO Step 2
*** TODO Step 3
> Thanks and I look forward to your response
More details of my setup can be found at
http://doc.norang.ca/org-mode.html
Regards,
Bernt
prev parent reply other threads:[~2011-01-22 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 22:20 Org-for GTD: Some implementation questions Chris Barber
2011-01-22 1:27 ` Bernt Hansen [this message]
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=8739ol7mno.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=c.barber80@gmail.com \
--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 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).