emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Creating prioritized todo list from GTD project/next action list
Date: Mon, 12 Mar 2007 10:13:25 +0100	[thread overview]
Message-ID: <87slcasu2y.fsf@bzg.ath.cx> (raw)
In-Reply-To: <b2e202b30703071930u70cb6bafpa8cb841139fcdca9@mail.gmail.com> (Scott Jaderholm's message of "Wed\, 7 Mar 2007 20\:30\:50 -0700")

Hi Scott,

"Scott Jaderholm" <jaderholm@gmail.com> writes:

> I've tried tagging TODOs with :today:, but you can't reorder them in the
> agenda match tag window. What I normally do now is schedule the TODOs for
> today and then I archive them in the agenda view with $ to complete
> them. The biggest problem with this is that I can't reorder the scheduled
> TODOs to reflect the priority or order in which I want to do them, and I
> clutter up my calendar view of the day.

Here is a brief overview of how i use org-mode to solve (workaround?) the
issue you raised :

- I use a "NEXT" state for the next actions (i admittedly suppose most of
  the next actions should be done on ... today)

- Tags are only related to the context or the /kind/ of actions (:work:,
  :home: or :reading:, :writing:), making it easy to know what i can do
  depending on what i want to do

- I manually order the NEXT actions within a project so that they appear in
  the right order in the agenda view

- I manually order the project themselves (either within a file or by using
  C-c [ and C-c ]) so that projects appear in the right order

- I schedule a task iff it has to be done on a specific day.

Hope this helps, regards,

-- 
Bastien

      parent reply	other threads:[~2007-03-12  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  3:30 Creating prioritized todo list from GTD project/next action list Scott Jaderholm
2007-03-08  5:04 ` Claudine Chionh
2007-03-08  8:43 ` Creating prioritized todo list from GTD project/nextaction list Egli Christian (KIRO 43)
2007-03-12  9:13 ` Bastien [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=87slcasu2y.fsf@bzg.ath.cx \
    --to=bzg@altern.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).