From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:43939) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1isGX4-0005Ps-3j for emacs-orgmode@gnu.org; Thu, 16 Jan 2020 20:34:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1isGX2-0000og-MI for emacs-orgmode@gnu.org; Thu, 16 Jan 2020 20:34:41 -0500 Received: from mail-il1-x133.google.com ([2607:f8b0:4864:20::133]:44744) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1isGX2-0000kG-Hb for emacs-orgmode@gnu.org; Thu, 16 Jan 2020 20:34:40 -0500 Received: by mail-il1-x133.google.com with SMTP id z12so19960212iln.11 for ; Thu, 16 Jan 2020 17:34:39 -0800 (PST) MIME-Version: 1.0 From: Gary Cheng Date: Thu, 16 Jan 2020 20:34:27 -0500 Message-ID: Subject: [bug] org-agenda-sorting-strategy sorting incorrectly? Content-Type: multipart/alternative; boundary="000000000000e93b40059c4bf19f" List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+kyle=kyleam.com@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org --000000000000e93b40059c4bf19f Content-Type: text/plain; charset="UTF-8" With the following: (setq org-agenda-sorting-strategy '((agenda time-up deadline-down scheduled-down habit-down priority-down category-keep) (todo priority-down category-keep) (tags priority-down category-keep) (search category-keep))) The `time-up` is correctly shown first; however, all scheduled items are shown next as opposed to all deadline items (the order should be the other way around). Also, it is unfortunate that there is no symbol for upcoming deadline items to differentiate them from past deadline items. Since they are considered "earliest", the sorting goes from "In 5 days... -> In 3 days... -> 2 days ago --> 4 days ago", which is rarely useful. There is no way to sort just items past due date "2 days ago --> 4 days ago --> 5 days ago", which is a much more common workflow (e.g. looking down the agenda, the more salvageable recent deadline items are at the top). It is more sensible to just limit deadline items to items due today or the past, and have a separate symbol for upcoming deadlines (i.e. "upcoming-deadline-down" and "upcoming-deadline-up"). Then, one can e.g. put all upcoming deadline items at the bottom of the agenda because he wants to deal with items that are more relevant now. Currently on lorg-mode 9.3.1 (latest version of org-mode available as of this submission). --000000000000e93b40059c4bf19f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
With the following:

=C2=A0 =C2=A0 (setq org-agenda-= sorting-strategy '((agenda time-up deadline-down scheduled-down habit-d= own priority-down category-keep)
=C2=A0 =C2=A0 =C2=A0(todo priority-down= category-keep)
=C2=A0 =C2=A0 =C2=A0(tags priority-down category-keep)=C2=A0 =C2=A0 =C2=A0(search category-keep)))

The `time-up` is= correctly shown first; however, all scheduled items are shown next as oppo= sed to all deadline items (the order should be the other way around).
=

Also, it is unfortunate that there is no symbol for upc= oming deadline items to differentiate them from past deadline items. Since = they are considered "earliest", the sorting goes from "In 5 = days... -> In 3 days... -> 2 days ago --> 4 days ago", which = is rarely useful. There is no way to sort just items past due date "2 = days ago --> 4 days ago --> 5 days ago", which is a much more co= mmon workflow (e.g. looking down the agenda, the more salvageable recent de= adline items are at the top). It is more sensible to just limit deadline it= ems to items due today or the past, and have a separate symbol for upcoming= deadlines (i.e. "upcoming-deadline-down" and "upcoming-dead= line-up"). Then, one can e.g. put all upcoming deadline items at the b= ottom of the agenda because he wants to deal with items that are more relev= ant now.

Currently on lorg-mode 9.3.1 (latest vers= ion of org-mode available as of this submission).

<= div>
--000000000000e93b40059c4bf19f--