emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Keith David Bershatsky <esq@lawlist.com>
To: emacs-orgmode@gnu.org
Subject: `org-agenda-sorting-strategy` -- missing text properties.
Date: Sat, 06 Jun 2015 16:43:10 -0700	[thread overview]
Message-ID: <m2d2182yk1.wl%esq@lawlist.com> (raw)

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

             reply	other threads:[~2015-06-06 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06 23:43 Keith David Bershatsky [this message]
2015-06-09  7:28 ` `org-agenda-sorting-strategy` -- missing text properties Nicolas Goaziou

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=m2d2182yk1.wl%esq@lawlist.com \
    --to=esq@lawlist.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).