From: Adam Spiers <orgmode@adamspiers.org>
To: emacs-orgmode@gnu.org
Subject: Re: SOMEDAY/MAYBE vs. low priorities
Date: Mon, 31 Dec 2007 17:09:48 +0000 [thread overview]
Message-ID: <20071231170948.GP20947@atlantic.linksys.moosehall> (raw)
In-Reply-To: <20071231144414.GM20947@atlantic.linksys.moosehall>
(More Structured Procrastination... ;-)
Adam Spiers (orgmode@adamspiers.org) wrote:
> And on top of that, I need a way of marking a "someday" or "maybe"
> task/project as already STARTED or WAITING etc., which is why I
> wrote:
>
> > - Priorities become truly orthogonal to workflow, e.g. if your
> > workflow keywords are PROJECT, PROJDONE, NEXT, STARTED, WAITING,
> > DONE etc. then you can mark any of these as someday/maybe
> > priority. This is quite a big advantage AFAICS.
Here's another case study for treating someday/maybe as priorities
rather than as keywords; best illustrated by example:
* PROJECT [#A] This is an urgent project
** but it's stuck since we don't have any NEXT actions yet.
** However we do have:
*** SOMEDAY some ideas about what might need doing later on
*** MAYBE here's another idea we're not sure about yet
* SOMEDAY This is an unimportant project
** Our NEXT actions are still SOMEDAY/MAYBE actions
** so is it stuck or not?
** Technically yes, but do we care?
since the whole project is only a SOMEDAY.
*** SOMEDAY when the project comes alive, this becomes a NEXT
*** MAYBE here's another idea we're not sure about yet
In the "someday" project above, notice how the distinction between the
unimportant project and its as yet unimportant subtasks is blurred.
That makes for inaccurate search results. How would we configure
`org-agenda-stuck-projects' to get the desired results?
Now compare with:
* PROJECT [#A] This is an urgent project
** but it's stuck since we don't have any NEXT actions yet
** of priority #C or higher.
** However we do have:
*** NEXT [#D] some ideas about what might need doing later on
*** NEXT [#E] here's another idea we're not sure about yet
* PROJECT [#D] This is an unimportant "someday" project
*** SOMEDAY when the project comes alive, this "someday" action becomes a NEXT
*** NEXT [#D] or we could mark it like this
*** NEXT or even this, which would appear in searches for unprioritised items
*** NEXT [#E] here's another "maybe" idea we're not sure about yet
I don't really know what's best, but hopefully this is all food for
thought.
Happy New Year to all!
Adam
next prev parent reply other threads:[~2007-12-31 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 18:11 SOMEDAY/MAYBE vs. low priorities Adam Spiers
2007-12-30 21:10 ` Eddward DeVilla
2007-12-30 22:44 ` Pete Phillips
2007-12-31 14:44 ` Adam Spiers
2007-12-31 17:09 ` Adam Spiers [this message]
2007-12-31 17:15 ` Adam Spiers
2007-12-31 17:25 ` Manish
2007-12-31 19:01 ` Pete Phillips
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=20071231170948.GP20947@atlantic.linksys.moosehall \
--to=orgmode@adamspiers.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.