From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric J Haywiser Subject: Behavior Change/Bug: Agenda sorting of deadline items v > 4.73 Date: Thu, 31 Jan 2008 10:33:51 -0500 (EST) Message-ID: References: <20080131103218.GB21734@atlantic.linksys.moosehall> <8616E01A-5786-49E5-BA14-C5968EA2FE4A@science.uva.nl> <20080131120310.GD21734@atlantic.linksys.moosehall> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JKbQd-0002G4-S6 for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 10:34:15 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKbQd-0002FD-7B for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 10:34:15 -0500 Received: from biscayne-one-station.mit.edu ([18.7.7.80]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JKbQd-0003uV-3O for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 10:34:15 -0500 Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.13.6/8.9.2) with ESMTP id m0VFXqeN016709 for ; Thu, 31 Jan 2008 10:33:52 -0500 (EST) Received: from mint-square.mit.edu (MINT-SQUARE.MIT.EDU [18.7.18.71]) (authenticated bits=56) (User authenticated as ejh1@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id m0VFXp8X014629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 31 Jan 2008 10:33:52 -0500 (EST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org I've noticed a change in the way org displays deadlines in the agenda starting sometime after v4.73. Before that time deadlines were displayed in chronological order. This is the behavior I expect. In the current org-5.16a and a number of versions before that the agenda items are in somewhat random order. Order seems to depend on both the date and the order of the deadlines in the org file. Apologies if this was an intended design change and I missed the announcement. It has been difficult to keep up with all the wonderful advancements in org. Perhaps I need to configure some variable to get back to the original behavior? Behavior in 5.16a Thursday 31 January 2008 deadline-order-bug:In -730 d.: Jan One DEADLINE: <2006-01-31 Thu> deadline-order-bug:In -365 d.: Jan Two DEADLINE: <2007-01-31 Thu> deadline-order-bug:Deadline: Jan Three DEADLINE: <2008-01-31 Thu> deadline-order-bug:In -715 d.: Feb One DEADLINE: <2006-02-15 Thu> deadline-order-bug:In -350 d.: Feb Two DEADLINE: <2007-02-15 Thu> deadline-order-bug:In 15 d.: Feb Three DEADLINE: <2008-02-15 Thu> deadline-order-bug:In 366 d.: Jan Four DEADLINE: <2009-01-31 Thu> deadline-order-bug:In 381 d.: Feb Four DEADLINE: <2009-02-15 Thu> Behavior in 4.67c Thursday 31 January 2008 deadline-order-bug:In -730 d.: Jan One DEADLINE: <2006-01-31 Thu> deadline-order-bug:In -715 d.: Feb One DEADLINE: <2006-02-15 Thu> deadline-order-bug:In -365 d.: Jan Two DEADLINE: <2007-01-31 Thu> deadline-order-bug:In -350 d.: Feb Two DEADLINE: <2007-02-15 Thu> deadline-order-bug:Deadline: Jan Three DEADLINE: <2008-01-31 Thu> deadline-order-bug:In 15 d.: Feb Three DEADLINE: <2008-02-15 Thu> deadline-order-bug:In 366 d.: Jan Four DEADLINE: <2009-01-31 Thu> deadline-order-bug:In 381 d.: Feb Four DEADLINE: <2009-02-15 Thu> Also note that something like the <= v4.73 behavior can be achieved by inserting the older org-agenda-get-deadlines function into 5.16a, but it seems to have some side effects. Note the missing Deadline item for TODAY aka "Jan Three" below. Regardless I believe the bug, if present, may lie in that function. I don't yet understand the internals. Behavior in 5.16a with o-a-g-d from 4.67c overlayed Thursday 31 January 2008 deadline-order-bug:In -730 d.: Jan One DEADLINE: <2006-01-31 Thu> deadline-order-bug:In -715 d.: Feb One DEADLINE: <2006-02-15 Thu> deadline-order-bug:In -365 d.: Jan Two DEADLINE: <2007-01-31 Thu> deadline-order-bug:In -350 d.: Feb Two DEADLINE: <2007-02-15 Thu> deadline-order-bug:In 15 d.: Feb Three DEADLINE: <2008-02-15 Thu> deadline-order-bug:In 366 d.: Jan Four DEADLINE: <2009-01-31 Thu> deadline-order-bug:In 381 d.: Feb Four DEADLINE: <2009-02-15 Thu> The following is the example org file to generate this behavior. Also, You will need to (set-variable org-deadline-warning-days 1000) to test this. * Jan One DEADLINE: <2006-01-31 Thu> * Jan Two DEADLINE: <2007-01-31 Thu> * Jan Three DEADLINE: <2008-01-31 Thu> * Jan Four DEADLINE: <2009-01-31 Thu> * Feb Three DEADLINE: <2008-02-15 Thu> * Feb One DEADLINE: <2006-02-15 Thu> * Feb Two DEADLINE: <2007-02-15 Thu> * Feb Four DEADLINE: <2009-02-15 Thu> Thanks. P.S. Examples from emacs22, but similar problems in e21.