Bastien <b...@gnu.org> writes:
No Wayman <iarchivedmywholel...@gmail.com> writes:
Well, back to square one -- the "fix" breaks setting the end
time
of an existing schedule timestamp for me with.
I reverted it as 771c66f79.
Unfortunate, but I see the same breakage with the patch. I stepped
through trying to set and end time of an existing schedule
timestamp
and I think the problem may be in `org-read-date-analyze'.
The sections commented:
;; Check if a time range is given as a duration
;; Check if there is a time range
Might be where the problem is.
Not 100% on why yet as I don't have deep knowledge of how this
function is
supposed to work and it is a little opaque. I'll keep researching
and see if I can come up with anything.
