emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Automatically Increasing Priority
Date: Wed, 25 Jun 2014 09:37:39 -0700	[thread overview]
Message-ID: <87egydrlm3.fsf@berkeley.edu> (raw)
In-Reply-To: 87k385l2sv.fsf@quasar.esben-stien.name

Hi Esben,

Esben Stien <b0ef@esben-stien.name> writes:

> Does there exist such a concept of automatically increasing priority
> after a while?

I'm not aware of any way of automatically changing the priority of a
headline, though if you really need this, it looks like it would be
fairly simple to do it in Elisp using the `org-map-entries' and
`org-priority' functions.  

I have the same problem you do: the priorities feature does not really
map well onto my work.  I used to capture a priority with every item,
but I've recently stopped doing that because I found it didn't make
sense for me.  I think it makes more sense to assign priorities
manually, when you're in a context of figuring out which tasks to work
on, rather than in a context of recording tasks to be done in the
future.

I suggest that, if you aren't doing this already, you put deadlines on
your TODO items, rather than priorities, and then sort the agenda by
deadline.  This has the advantage that it `prioritizes' all your tasks
in a natural way in the agenda: anything due soon (or past due) comes up
before things that are due later on.  So if you assign every task an
initial deadline, its `priority' will go up automatically, as time
passes.  When it comes due, you can always readjust the deadline if your
initial estimate didn't work out.

It's also useful, I think, to make one of your tasks a recurring weekly
review: go through all your other tasks, make sure you still want to do
them, adjust deadlines as necessary, etc.  If you find you still want
priority cookies in addition to deadlines, you could assign them during
this review for tasks due in the upcoming week.  At that point, you'll
be in a context where assigning priorities to these items makes more
sense, since you'll be looking at the other tasks each task competes
with.

Hope that helps!

Best,
Richard


(If possible, please encrypt your reply to me using my PGP key:
Key ID: CF6FA646
Fingerprint: 9969 43E1 CF6F A646.
See http://www.ocf.berkeley.edu/~rwl/encryption.html for more information.)

     prev parent reply	other threads:[~2014-06-25 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 10:08 Automatically Increasing Priority Esben Stien
2014-06-25 16:37 ` Richard Lawrence [this message]

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=87egydrlm3.fsf@berkeley.edu \
    --to=richard.lawrence@berkeley.edu \
    --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

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).