From: Bernt Hansen <firstname.lastname@example.org>
To: Jacek Generowicz <email@example.com>
Subject: Re: Sort TODOs in agenda day
Date: Wed, 01 Feb 2012 07:51:59 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <944812b5-d705-48d5-8ad0-aa5305f43352@CERNFE23.cern.ch> (Jacek Generowicz's message of "Wed, 1 Feb 2012 11:02:31 +0100")
Jacek Generowicz <email@example.com> writes:
> At Tue, 31 Jan 2012 12:39:48 -0500,
> Bernt Hansen wrote:
>> Jacek Generowicz <firstname.lastname@example.org> writes:
>> > Yes, but how do I instruct it to apply one strategy (time-up) to those
>> > items which appear in the time-grid portion of the day's display (the
>> > appointments), and a different one to the other entries (scheduled
>> > TODOs, deadlines)? Specifically, by adding a command to
>> > org-agenda-custom-commands
>> > which contains something like
>> > ((agenda ""
>> > ((org-agenda-sorting-strategy '(effort-up)))))
>> > messes up the time ordering of appointments for that command.
>> I have a fairly complicated sorting function which gets the order of
>> items exactly how I want to see them on the agenda.
>> The gory details are here:
> I see. Should I infer that org-mode doesn't provide any features for
> applying different strategies to different portions of single day's
> display in the agenda?
> In other words there are no hooks into the standard agenda sorting
> strategy, and if you want to modify its behaviour you essentially have
> to roll your own from scratch, duplicating much of the original
Not necessarily, if the standard sorting mechanism with an appropriate
setting for org-agenda-sorting-strategy does what you need then there is
no reason to create a user-defined sorting function (which is what I
You can add BOTH time-up and effort-up to the sorting strategy for the
agenda and time will prevail - for items with a time, and effort will be
the next sorting criteria.
Have you tried this?
;; Sorting order for tasks on the agenda
(quote ((agenda time-up effort-up))))
When I was first experimented with the sorting strategy I used the
customize interface to set it for the current session only and looked at
the result of my agenda with the new setting.
The reason I define and use a user-defined-up sorting function is I want
complete control over where each type of item goes in my agenda.
My setting for the agenda is below:
(quote ((agenda habit-down time-up user-defined-up priority-down effort-up category-keep)
(todo category-up priority-down effort-up)
(tags category-up priority-down effort-up)
so for the agenda daily view habits are at the bottom, and timed items
are at the top, then my user-defined sorting function sorts what is left
for the middle section of the list in the following order:
- items with no schedule/deadline and timestamped for today
- deadlines for today
- late deadlines
- scheduled items for today
- late scheduled items
- and pending deadlines last
next prev parent reply other threads:[~2012-02-01 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 12:30 Sort TODOs in agenda day Jacek Generowicz
2012-01-31 0:32 ` Bernt Hansen
2012-01-31 8:03 ` Jacek Generowicz
2012-01-31 17:39 ` Bernt Hansen
2012-02-01 10:02 ` Jacek Generowicz
2012-02-01 12:51 ` Bernt Hansen [this message]
2012-02-02 9:24 ` Jacek Generowicz
2012-02-03 2:06 ` Bernt Hansen
2012-02-02 18:11 ` Samuel Wales
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).