From: Manish <mailtomanish.sharma@gmail.com>
To: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Sorting agenda items
Date: Fri, 18 Apr 2008 12:36:24 +0530 [thread overview]
Message-ID: <e7cdbe30804180006s3c75f711wae2ef0a8b4996b65@mail.gmail.com> (raw)
In-Reply-To: <e7cdbe30804171329n2fad29a8p63992980b46dde0f@mail.gmail.com>
On Fri, Apr 18, 2008 at 1:59 AM, Manish wrote:
> Hello All,
>
> I would like to set up a daily agenda view with todos sorted in the
> following order:
>
> 1. Timed TODOs
> 2. DEADLINES
> 3. TODO type - STARTED
> 4. TODO type - NEXT
> 5. TODO type - TODO
>
> I could find/figure out how to do #1 and #2 but #3-5 escape me. I
> hope I did not miss it in the manual.
>
> The whole idea is to spend minimum brain cycles while picking up
> next item from the agenda. One way that makes sense for me is to
> reduce the size of region that I would scan while picking up next item
> (i.e. set of NEXT todos). I think it's possible if one uses tags to
> mark task state changes. Not sure how to do it with TODO keywords. I
> wonder if people just pick up whatever is on the top of the agenda or
> scan the whole list everytime you want to pick up next task?
>
> Hope it made sense.
>
While searching for how people deal with this, I found this almost 3
year old wonderful post about strategies to approach your tasks:
http://www.murtworld.com/2005/04/revolving-workflow-strategies.php .
And with latest sorting options "effort-up" and "effort-down", I
guess I have a sensible way to decide which next actions to pick up.
Thanks Carsten. I am thinking it's even better than sorting on TODO
keywords.
Now if only I can sort tasks based on their creation dates as
well. ;-) Just kidding.
-- Manish
next prev parent reply other threads:[~2008-04-18 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 20:29 Sorting agenda items Manish
2008-04-18 7:06 ` Manish [this message]
2008-04-18 16:02 ` Carsten Dominik
2008-04-19 8:43 ` Manish
2008-04-23 12:59 ` 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=e7cdbe30804180006s3c75f711wae2ef0a8b4996b65@mail.gmail.com \
--to=mailtomanish.sharma@gmail.com \
--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).