From: "Carsten Dominik" <dominik@science.uva.nl>
To: "Egli Christian (KIRO 41)" <christian.egli@credit-suisse.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Patch] Sort agenda items by todo-state
Date: Thu, 22 Nov 2007 08:35:03 +0100 [thread overview]
Message-ID: <acf852aa0711212335s480866a2s1a0ef598e0970fdc@mail.gmail.com> (raw)
In-Reply-To: <52D89C75FEE9444E8D9C016E3730098306CE6B@chsa1036.share.beluni.net>
I for one do like the patch, so please clean it up and I would be
happy to take it
(if you have signed the papers with the FSF, that is :-(
- Carsten
On Nov 21, 2007 1:13 PM, Egli Christian (KIRO 41)
<christian.egli@credit-suisse.com> wrote:
>
>
>
>
> * Introduction
> I live in my org agenda view and I schedule all my tasks to the
> day that I want to do them. I also would like to see my
> achievements so I keep the TODOs that are done in the agenda
> view. However I would like them to get out of the way so that I
> can better see the tasks that are still open. That is why for a
> long time I've been wanting to sort the agenda items by todo
> state.
>
> * Patch
> I finally looked at the code and realized that this was not very
> hard to do. The following patch (against 5.13i) implements a new
> org-agenda-sorting-strategy that allows you to sort agenda items
> by todo-state.
>
> * Notes
> The patch is basically a "works-for-me" implementation. It only
> sorts todo and scheduled items. It should probably do the same
> for deadlines. Maybe even for timestamps?
>
> The doc strings need to be updated.
>
> Carsten at one time talked about implementing this feature by
> using priorities, i.e. factoring the todo-state into the priority
> (which uses the actual priority plus some calculation based on
> how many days the task is overdue). This patch takes a different
> route.
>
> The sorting is done by comparing the todo-state of the items. It
> first orders them by done state, i.e. all done items come after
> (or before) the items that are not done. After that it compares
> the todo-states with a string compare. This should probably use
> some kind of ordering information from the relevant
> org-todo-keywords sequence.
>
> * Conclusion
> So the basic question is: Should I clean up this patch to get it
> included? Is the proposed route (of not taking the priorities)
> ok? And finally: How do I sort taking the sequence order into
> consideration?
>
> Christian
>
>
> <<org.diff>>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
prev parent reply other threads:[~2007-11-22 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 12:13 [Patch] Sort agenda items by todo-state Egli Christian (KIRO 41)
2007-11-22 7:35 ` Carsten Dominik [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=acf852aa0711212335s480866a2s1a0ef598e0970fdc@mail.gmail.com \
--to=dominik@science.uva.nl \
--cc=christian.egli@credit-suisse.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).