From: Stephan Schmitt <drmabuse@cs.tu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Re: Interpretation of priorities in org-mode
Date: Tue, 31 Jul 2007 19:38:48 +0200 [thread overview]
Message-ID: <46AF73A8.3070705@cs.tu-berlin.de> (raw)
In-Reply-To: <E1IFuCH-0002uJ-Ki@mail.zrz.tu-berlin.de> (auto-added)
Hello,
I think there are two possible interpretations of 'priority', /importance/ and
/urgency/.
It is up to the user which is preferred. You propose the interpretation as
urgency: "I have to do that thing today/this week/sometime". Importance may
come into play with your daily decision, what to do next. The advantage of this
approach is the better quantifiability of 'urgency'.
At the moment in org-mode you have to opt for one interpretation. But with the
fresh and cool property feature in org-mode it should be possible to incorporate
both aspects together. Somehow.
Just a thought, though.
Greetings,
Stephan
Piotr Zielinski wrote:
> Hi.
>
> 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've been recently experimenting with a different interpretation of
> priorities: #B = tasks to do today, #C = tasks to do this week, #D =
> all the rest, default. #A is reserved at the moment. One good thing
> about this system is a clearer interpretation of priorities. Another is
> that it separates the action of inserting new items into your todo
> list and that of assigning a particular priority to them. In
> particular, at the beginning of each day, you can look at your list of
> todos/deadlines/scheduled, and pick a few to complete on that day by
> giving them the #B priority. At any time of the day, the agenda will
> show you these #B items clearly separated from the rest. Previously,
> I had to do a mental rescanning of the agenda items each time I
> was wondering "what do I have to do now", which was rather stressful.
>
> Of course, I've tried this only for a couple of days, so my
> conclusions might be completely bogus. Maybe there is a better way
> than priorities to mark items as "to complete today". I'd definitely
> like to know what others think about it.
next parent reply other threads:[~2007-07-31 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1IFuCH-0002uJ-Ki@mail.zrz.tu-berlin.de>
2007-07-31 17:38 ` Stephan Schmitt [this message]
2007-08-01 14:47 Interpretation of priorities in org-mode Renzo Been
-- strict thread matches above, loose matches on Subject: below --
2007-07-30 17:53 Piotr Zielinski
2007-08-01 0:22 ` Bastien
2007-08-01 14:58 ` Jason F. McBrayer
2007-08-01 15:24 ` Piotr Zielinski
2007-08-02 12:13 ` Egli Christian (KIRO 41)
2007-08-09 5:05 ` Carsten Dominik
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=46AF73A8.3070705@cs.tu-berlin.de \
--to=drmabuse@cs.tu-berlin.de \
--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).