From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith David Bershatsky Subject: `org-agenda-sorting-strategy` -- missing text properties. Date: Sat, 06 Jun 2015 16:43:10 -0700 Message-ID: Mime-Version: 1.0 (generated by - "") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57880) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z1NkC-0000RV-LK for emacs-orgmode@gnu.org; Sat, 06 Jun 2015 19:43:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z1Nk9-0000Mu-FS for emacs-orgmode@gnu.org; Sat, 06 Jun 2015 19:43:16 -0400 Received: from cobb.liquidweb.com ([50.28.13.150]:36505) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z1Nk9-0000Ml-7d for emacs-orgmode@gnu.org; Sat, 06 Jun 2015 19:43:13 -0400 Received: from cpe-45-48-239-195.socal.res.rr.com ([45.48.239.195]:49535 helo=server.local.localhost) by cobb.liquidweb.com with esmtp (Exim 4.82) (envelope-from ) id 1Z1Nk5-0006bM-Jo for emacs-orgmode@gnu.org; Sat, 06 Jun 2015 19:43:09 -0400 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org There are nine (9) places in org-version 8.2.10 (which is included within Emacs public release 24.5.1) that could use some attention by the org-mode team. I have fixed it in my own custom version of org-mode, but I have seen a couple of questions recently on the Emacs forums by users wondering why the sorting strategy does not always work in various situations. The reason why users are having problems is because not all of the text properties are added during the data gathering process that are needed for `org-entries-lessp` to do its job. I would suggest that the org-mode team look at all nine (9) locations where `org-add-props txt props` is used and try to add as many additional text properties as possible for members of the `org-agenda-sorting-strategy`. Of course, the org-mode team will need to make decisions and code will need to be added to gather/assign the applicable values before the text-properties can be assigned. In a nutshell, if the `org-agenda-sorting-strategy` offers a sorting type, then an effort should be made within the code to assign those corresponding text properties when the data is gathered. Decisions by the org-mode team, include, but are not limited to, which timestamp will be used for a sorting date when both deadline and scheduled are present -- perhaps even a new sorting thing-a-ma-jig to deal with that special situation should be created. Thanks, Keith