From: "David A. Thompson" <thompdump@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Jeff Horn <jrhorn424@gmail.com>
Subject: Re: specifying priority with template expansion
Date: Fri, 03 Dec 2010 14:42:57 -0800 [thread overview]
Message-ID: <4CF97271.2020803@gmail.com> (raw)
In-Reply-To: <AANLkTikZm03Aje9BFn6c88Qa=4_UKFLRuZ6yLQemG1PP@mail.gmail.com>
On 12/03/2010 12:40 PM, Jeff Horn wrote:
> Can you give us a better idea of the use case? As I understand,
> unprioritzed todos count as "B" by default. Since most of my tasks
> have a priority of B, I've never found setting priorities to be
> helpful until I sit down to review my work for the day.
>
> I prioritize items that are important (or urgent) with A at the
> beginning of the day (no more than a couple, usually). Most items are
> "B" and rarely more than half of those get done.
>
> If I want to "sink" an item but keep it scheduled, it gets a priority of "C".
Most of my todos are neither associated with deadlines nor are they
scheduled. Schedules and deadlines have seemed a more time-intensive way
to go relative to setting priorities (but perhaps this is a 'Green Eggs
and Ham' thing?)
> These are often things I do not know when recording an item.
I guess the main difference is that I generally am typically able to
recognize, when recording a todo, whether it's in the 'urgent/asap' pile
(A), the 'try-and-get-it-done-sometime-soon' pile (B), or in a
'sure-would-be-nice-to-get-it-done' pile (C). Given that, it seemed both
logical and more efficient to immediately prioritize the item rather
than going back later and prioritizing the item.
Thanks for any additional thoughts/suggestions...
- Alan
>
next prev parent reply other threads:[~2010-12-03 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 20:00 specifying priority with template expansion David A. Thompson
2010-12-03 20:40 ` Jeff Horn
2010-12-03 22:42 ` David A. Thompson [this message]
2010-12-04 18:37 ` Jeff Horn
2010-12-05 4:30 ` Memnon Anon
2010-12-06 10:00 ` 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=4CF97271.2020803@gmail.com \
--to=thompdump@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jrhorn424@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).