From: David O'Toole <dto@gnu.org>
To: emacs-orgmode@gnu.org
Subject: my simple GTD setup
Date: Fri, 28 Sep 2007 02:18:20 -0400 [thread overview]
Message-ID: <m3ps03gvo3.fsf@gnu.org> (raw)
I read through some of the available articles by people who use org
for GTD and decided to try it myself.
Two days ago I put together a very simple setup.
Screenshot at http://dto.freeshell.org/notebook/images/menu-shot.png
Elisp snippets at bottom of message.
Details:
- I use the TODO keywords as a "task status".
These are TODO, MAYBE, WAITING, NEXT, DONE.
"NEXT" is specially fontified so that it stands out.
I find it convenient to use org-mouse to change keywords.
- I use tags for contexts. I don't worry about not having a precise
definition of what a context is; it could be a place, a tool, a
person, a project, or whatever.
- I put almost everything in One Big Org File. This is the biggest
change from my old style. I used to have one org file per project,
with the "webpage" stuff in the top half, and the TODO items jammed
all at the end of the file in a huge mess.
Now I am using foo.org as the webpage and notes file, whereas the
workflow structure and scheduling for "foo" go into the foo section
of my main file "dto.org". I think this separation will help each
file be cleaner, and bring together all my workflows into one
hierarchically organized clickable buffer.
- I am having trouble with searching for all the "NEXT" keyword
items, which is all I really need to complete my setup. I can see
the list of NEXT actions, but not what project they come from or
what tags they have. So it can be tricky to understand what the
task means out of context. Should I use a tag to represent each
project, or properties, or what?
There is so much other stuff like tables, properties, etc that I'm not
sure what to do with yet, but I'm sure I'll find something :-)
> (setq org-hide-leading-stars t)
> (setq org-todo-keywords '((sequence "TODO" "MAYBE" "WAITING" "NEXT" "DONE")))
> (setq org-tag-alist '(("STUDIO" . ?s)
> ("COMPUTER" . ?c)
> ("MAIL" . ?m)
> ("HOME" . ?h)
> ("PROJECT" . ?p)
> ("READING" . ?r)
> ("DVD" . ?r)))
> (setf org-special-ctrl-a/e t)
> (setf org-todo-keyword-faces '(("NEXT" . (:foreground "yellow" :background "red" :bold t :weight bold))))
--
David O'Toole
dto@gnu.org
http://dto.freeshell.org/notebook/
next reply other threads:[~2007-09-28 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 6:18 David O'Toole [this message]
2007-09-28 12:50 ` my simple GTD setup Dan Griswold
[not found] ` <b6c377310709272344s41cc1647y809343e0e9c3bf86@mail.gmail.com>
2007-09-28 15:30 ` David O'Toole
2007-09-29 13:50 ` Bastien
2007-09-29 23:36 ` Bernt Hansen
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=m3ps03gvo3.fsf@gnu.org \
--to=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 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).