From: jmcbray@carcosa.net (Jason F. McBrayer)
To: emacs-orgmode@gnu.org
Subject: Re: Interpretation of priorities in org-mode
Date: Wed, 01 Aug 2007 10:58:09 -0400 [thread overview]
Message-ID: <m1ejinpaim.fsf@bertrand.carcosa.net> (raw)
In-Reply-To: <3c12eb8d0707301053q29699a34qe0a6801bd0fbb7@mail.gmail.com> (Piotr Zielinski's message of "Mon, 30 Jul 2007 18:53:37 +0100")
"Piotr Zielinski" <piotr.zielinski@gmail.com> writes:
> I'd like to find out how different people use priorities (#A, #B, ...)
> in org-mode. I've always assumed the standard interpretation (#A =
> high priority, #B = medium, #C = low). However, the problem with this
> approach is that what "high priority" means is not well defined, and
> if you are not careful, then all your items will quickly become high
> priority, which defeats the whole point.
I don't really use priorities at all, since I'm using org-mode to do
GTD. If something has to be done today, then that's a deadline, not a
priority. If I don't need or want to get something done /in the next
week/, it probably shouldn't be crowding up my todo-lists at all, and
making it harder for me to find things I should be doing; it should be
on my someday/maybe list.
--
+-----------------------------------------------------------+
| Jason F. McBrayer jmcbray@carcosa.net |
| If someone conquers a thousand times a thousand others in |
| battle, and someone else conquers himself, the latter one |
| is the greatest of all conquerors. --- The Dhammapada |
next prev parent reply other threads:[~2007-08-01 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 17:53 Interpretation of priorities in org-mode Piotr Zielinski
2007-08-01 0:22 ` Bastien
2007-08-01 14:58 ` Jason F. McBrayer [this message]
2007-08-01 15:24 ` Piotr Zielinski
2007-08-02 12:13 ` Egli Christian (KIRO 41)
2007-08-09 5:05 ` Carsten Dominik
[not found] <E1IFuCH-0002uJ-Ki@mail.zrz.tu-berlin.de>
2007-07-31 17:38 ` Stephan Schmitt
-- strict thread matches above, loose matches on Subject: below --
2007-08-01 14:47 Renzo Been
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=m1ejinpaim.fsf@bertrand.carcosa.net \
--to=jmcbray@carcosa.net \
--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).