From: Bastien <bzg@altern.org>
To: Piotr Zielinski <piotr.zielinski@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Interpretation of priorities in org-mode
Date: Wed, 01 Aug 2007 02:22:36 +0200 [thread overview]
Message-ID: <87lkcwxfw3.fsf@bzg.ath.cx> (raw)
In-Reply-To: <3c12eb8d0707301053q29699a34qe0a6801bd0fbb7@mail.gmail.com> (Piotr Zielinski's message of "Mon\, 30 Jul 2007 18\:53\:37 +0100")
Hi Piotr,
"Piotr Zielinski" <piotr.zielinski@gmail.com> writes:
> 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.
When i first started using priorities, i was also leaned to misuse them
as you describe, and my file ended up with top priorities everywhere.
After a while, i discover it was better:
1. not to upgrade priorities too easily;
2. not trying to make them do an other job than their job.
Let me explain myself a bit.
The #1 advice seems obvious but it is hard to stick to it. One problem
comes from Org-mode itself, because it makes it soooo easy to upgrade a
priority that you often feel like upgrading one -- instead of completing
the task under it :)
Another problem comes from the fact that priority are dependant from
each others. I think it's better to have something around 10%-[#A],
20%-[#B], and 30%-[#C], and changing the priority of a few tasks might
disturb the balance.
So here comes the #2 advice. Because i noticed that the reflex of
upgrading too many [#B] to [#A] was just a way to make my Org files
"say" something else (yes, my Org files *speak*), like "Do it next!"
(which should be said by a TODO keyword) or "Do it today, you lazy
bum!" (which could be said by the agenda...)
So i try to keep a reasonable number of high-prioritized tasks and if i
feel like i start to "upgrade" indecently, then i think twice about why
i'm doing this.
The thing is that i mainly use the priority system to have a useful
display of the agenda view:
(setq org-agenda-sorting-strategy
'((agenda time-up priority-down)
(todo priority-down)
(tags priority-down)))
(Okay, all of this is very nice but here is the truth: i got *tons* of
chaotic tasks under misused priorities... but at least you get the way
i would like to use them :)
PS: just thinking: another way to use priorities could be to make lower
tasks *dependant* (in they order of execution) from higher tasks. But i
would prefer to make this dependance visible by using the display order,
i.e. one task "after" another.
Regards,
--
Bastien
next prev parent reply other threads:[~2007-08-01 0:22 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 [this message]
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
[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=87lkcwxfw3.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=piotr.zielinski@gmail.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
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).