From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: Re: SOMEDAY/MAYBE vs. low priorities Date: Mon, 31 Dec 2007 17:09:48 +0000 Message-ID: <20071231170948.GP20947@atlantic.linksys.moosehall> References: <20071230181116.GE20947@atlantic.linksys.moosehall> <26163.1199054673@localhost> <20071231144414.GM20947@atlantic.linksys.moosehall> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J9O9F-0006N0-FR for emacs-orgmode@gnu.org; Mon, 31 Dec 2007 12:09:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J9O9D-0006J2-7P for emacs-orgmode@gnu.org; Mon, 31 Dec 2007 12:09:56 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J9O9D-0006Ii-0s for emacs-orgmode@gnu.org; Mon, 31 Dec 2007 12:09:55 -0500 Received: from mail.beimborn.com ([70.84.38.100]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1J9O9B-0005rC-UJ for emacs-orgmode@gnu.org; Mon, 31 Dec 2007 12:09:54 -0500 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id lBVH9nLa027208 for ; Mon, 31 Dec 2007 11:09:49 -0600 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id lBVH9nuo027203 for emacs-orgmode@gnu.org; Mon, 31 Dec 2007 17:09:49 GMT Content-Disposition: inline In-Reply-To: <20071231144414.GM20947@atlantic.linksys.moosehall> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org (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