From: "Christopher M. Miles" <firstname.lastname@example.org> To: Bastien <email@example.com> Cc: Org Mode <firstname.lastname@example.org> Subject: [CLOSED] TEC fixed this problem. Date: Fri, 04 Feb 2022 13:33:52 +0800 [thread overview] Message-ID: <PAXPR08MB6640701C9B6542CAEE6450D5A3299@PAXPR08MB6640.eurprd08.prod.outlook.com> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1494 bytes --] Today, I found the Org Agenda sorting strategy problem is fixed by commit "1b675f0ca84d637a3780cf3590308116e232fcfd". Thanks, TEC Bastien <firstname.lastname@example.org> writes: > Hi, > > stardiviner <email@example.com> writes: > >> org-agenda-sorting-strategy bug? Cannot list deadline items before scheduled items. >> >> With the following: >> >> #+begin_src emacs-lisp >> (setq org-agenda-sorting-strategy >> '((agenda time-up deadline-up scheduled-down ts-up habit-down priority-down category-keep) >> (todo priority-down category-keep) >> (tags priority-down category-keep) >> (search category-keep)) >> org-agenda-sorting-strategy-selected >> '(time-up priority-down deadline-up scheduled-down ts-up habit-down category-keep)) >> #+end_src >> >> 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). > > Can you provide a more minimal configuration example, with the order > expected and the order you get? > > As said in the reddit thread, the output of complex sorting strategies > can be confusing, so being minimal here is the way to go. > > Thanks, -- [ stardiviner ] I try to make every word tell the meaning that I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-04 5:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-07 14:15 org-agenda-sorting-strategy's sorting of deadline and schedule is opposed stardiviner 2020-05-24 11:53 ` Bastien 2022-02-04 5:33 ` Christopher M. Miles [this message] 2022-02-07 8:00 ` [CLOSED] TEC fixed this problem Bastien
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=PAXPR08MB6640701C9B6542CAEE6450D5A3299@PAXPR08MB6640.eurprd08.prod.outlook.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [CLOSED] TEC fixed this problem.' \ /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
Code repositories for project(s) associated with this 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).