Derek Chen-Becker <[email protected]> writes: > I was just working on > https://list.orgmode.org/orgmode/87wn31up0d.fsf@localhost/ as a simple bug > to tackle, but now that I'm catching up on this thread should I wait until > some of the timestamp handling here has been addressed? I have a patch > ready for `org-timestamp-change' that I think is probably independent of > what you're discussing, but I can wait if it would complicate the current > review.
It should be more or less independent. I think one thing to watch out is that Morgan's code assumes that we should shift both timestamps by equal number of minutes/hours/etc. If org-timestamp-change does something else for any reason, this assumption may be broken. And the example from the linked thread indeed shows an example when it is the case CLOCK: [2023-03-25 Sat 21:40]--[2023-03-26 Sun 03:05] => 4:25 in some timezone will not follow the exact number of changes in minutes/hours when the end result falls within DST transition. I'd say that fixing that bug with org-timestamp-change will make life easier for Morgan's code as we can be confident that the time changes will match. -- 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>
