Bug: org-agenda-sort-notime-is-late is not correctly handled by timestamp comparison [9.4.6 (9.4.6-12-gdcc3a8-elpaplus @ /Users/charlestam/.emacs.d/elpa/org-plus-contrib-20210830/)]

org-agenda-sorting-strategy claims that scheduled-up (-down) causes items to be sorted in ascending (descending) order by scheduled timestamp. org-agenda-sort-notime-is-late claims that if it is non-nil, the absence of a timestamp is treated as being maximal. Instead, when using the scheduled-up

Re: Bug: Off-by-one when archiving to top level date [9.3.6 (9.3.6-17-g389288-elpa @ /home/charlestam/.emacs.d/elpa/org-20200224/)]

, 2020 at 5:44 AM Bastien wrote: > Hi Charles, > > sorry for the late feedback. > > Charles Tam writes: > > > I am archiving subtrees of my main Orgmode document to a top-level > > datetree in a secondary file. When I do so, I expect something like > > the

Bug: Off-by-one when archiving to top level date [9.3.6 (9.3.6-17-g389288-elpa @ /home/charlestam/.emacs.d/elpa/org-20200224/)]

I am archiving subtrees of my main Orgmode document to a top-level datetree in a secondary file. When I do so, I expect something like the following: * 2020 *** 2020-02 February (org-odd-levels-only t) * 2020-02-27 Thursday *** Archived Item But instead I get * 2020 *** 2020-02 February