Charles T <[email protected]> writes: > Yup, sorry for the wait. Here is a patch to make the change via text > properties.
Thanks for the update, and sorry for the delay on my side. > * org-agenda.el (4 functions): Account for full datetime when > comparing timestamps in todo-list. > (org-agenda-entry-get-agenda-timestamp): Retrieve a timestamp > instead of a datestamp. The original functionality has been > renamed to org-agenda-entry-get-agenda-datestamp, with all calls > to the original redirected there. This will be a breaking change. Let's not do it. What about simply adding an optional argument to org-agenda-entry-get-agenda-timestamp? That will also avoid code duplication. > (org-agenda-get-todos): Add a 'ts-datetime text property assignment. What about `org-agenda-get-timestamps', `org-agenda-get-scheduled', and `org-agenda-get-deadlines'? > +++ b/testing/examples/agenda-file3.org > @@ -0,0 +1,11 @@ > +* TODO three point five > +SCHEDULED: <2024-01-17 Wed 17:00> > + > +* TODO zero > +SCHEDULED: <2024-01-17 Wed 08:00> > + > +* TODO four point five > +SCHEDULED: <2024-03-14 Thu 01:00> > + > +* TODO two point five > +SCHEDULED: <2024-01-17 Wed 12:00> Please add other combinations like 1. SCHEDULED without time specified 2. DEADLINE with and without time specified 3. active timestamp 4. diary-style timestamp 5. headings without TODO keyword Also, please pay attention to the warnings when you run make test. You got some malformed (let ...) statements. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
