From: Adam Spiers <firstname.lastname@example.org> To: org-mode mailing list <email@example.com> Subject: SOMEDAY/MAYBE vs. low priorities Date: Sun, 30 Dec 2007 18:11:16 +0000 Message-ID: <20071230181116.GE20947@atlantic.linksys.moosehall> (raw) GTD methodology suggests having "someday" and "maybe" task buckets for things which you want to remember to do at some undetermined point in the future. So far I have implemented this in org-mode by using SOMEDAY and MAYBE keywords. However I have been deliberating whether in fact these states are simply low priorities in disguise, and whether as a result it would make more sense to use [#D] for "someday" and [#E] for "maybe", on the grounds that "someday" implies that you really do want to accomplish the task eventually, whereas "maybe" implies that you're not yet decided whether you care too much if it ever gets accomplished, and is hence lower priority than "someday" (and probably the lowest priority imaginable, in fact). Pros: - 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. Cons: - By default org agenda TODO searches will operate on all TODO entries, regardless of priority. This means that you'd have to customise every existing agenda view of TODOs to restrict to only priorities #A to #C, which would be very cumbersome. What do people think? Are there other pros/cons, and is there a clean solution to "generally" restricting TODO views to #C or higher priority?
next reply other threads:[~2007-12-30 18:11 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-30 18:11 Adam Spiers [this message] 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 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 List information: https://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20071230181116.GE20947@atlantic.linksys.moosehall \ --firstname.lastname@example.org \ --email@example.com \ /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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git