From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric J Haywiser Subject: Re: Behavior Change/Bug: Agenda sorting of deadline items v > 4.73 Date: Thu, 31 Jan 2008 18:20:11 -0500 (EST) Message-ID: References: <20080131103218.GB21734@atlantic.linksys.moosehall> <8616E01A-5786-49E5-BA14-C5968EA2FE4A@science.uva.nl> <20080131120310.GD21734@atlantic.linksys.moosehall> <803AD9DF-C436-4733-B83D-90DBB16ADC21@science.uva.nl> 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 1JKihp-00008H-0e for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 18:20:29 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKiho-00007L-JR for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 18:20:28 -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 1JKiho-0002KL-Ax for emacs-orgmode@gnu.org; Thu, 31 Jan 2008 18:20:28 -0500 In-Reply-To: <803AD9DF-C436-4733-B83D-90DBB16ADC21@science.uva.nl> 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: Carsten Dominik Cc: emacs-orgmode@gnu.org > Hi Eric, > > sorting should be by priority. > Please check your values of org-agenda-sorting-strategy, In both examples it is set to ((agenda time-up category-keep priority-down) (todo category-keep priority-down) (tags category-keep)) > and take a look at the priorities of the different items in the agenda and for the same org file, which is the only org file used to construct the agenda I find: Under 5.16a priorities >> Thursday 31 January 2008 1100>> deadline-order-bug:In -730 d.: Jan One DEADLINE: <2006-01-31 Thu> 1100>> deadline-order-bug:In -365 d.: Jan Two DEADLINE: <2007-01-31 Thu> 1100>> deadline-order-bug:Deadline: Jan Three DEADLINE: <2008-01-31 Thu> 1100>> deadline-order-bug:In -715 d.: Feb One DEADLINE: <2006-02-15 Thu> 1100>> deadline-order-bug:In -350 d.: Feb Two DEADLINE: <2007-02-15 Thu> 1009>> deadline-order-bug:In 15 d.: Feb Three DEADLINE: <2008-02-15 Thu> 1009>> deadline-order-bug:In 366 d.: Jan Four DEADLINE: <2009-01-31 Thu> 1006>> deadline-order-bug:In 381 d.: Feb Four DEADLINE: <2009-02-15 Thu> Under 4.67c priorites are >> Thursday 31 January 2008 1740>> deadline-order-bug:In -730 d.: Jan One DEADLINE: <2006-01-31 Thu> 1725>> deadline-order-bug:In -715 d.: Feb One DEADLINE: <2006-02-15 Thu> 1375>> deadline-order-bug:In -365 d.: Jan Two DEADLINE: <2007-01-31 Thu> 1360>> deadline-order-bug:In -350 d.: Feb Two DEADLINE: <2007-02-15 Thu> 1100>> deadline-order-bug:Deadline: Jan Three DEADLINE: <2008-01-31 Thu> 995>> deadline-order-bug:In 15 d.: Feb Three DEADLINE: <2008-02-15 Thu> 644>> deadline-order-bug:In 366 d.: Jan Four DEADLINE: <2009-01-31 Thu> 629>> deadline-order-bug:In 381 d.: Feb Four DEADLINE: <2009-02-15 Thu> > does not show what is wrong, I need to search, so let me know what ou find, So shouldn't the priorities be the same across versions for same org file and org-agenda-sorting-strategy values? Maybe someone else can duplicate this behavior with the org file that follows? Thanks! >> 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>