Peter Solodov <solo...@gmail.com> writes: > Changing `org-cancel-repeater' to work on all active timestamps makes > the most sense to me. The reason this came up at all is because org > changes order of timestamps, first timestamp is always the timestamp > that was changed last. If entry is a state where current code can handle > it correctly and then timestamp with repeater is shifted through a > normal user action (updating deadline or scheduled), then canceling with > repeater override is unexpectedly broken.
Fixed, on main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9c98b21460 -- Ihor Radchenko // yantar92, Org mode contributor, 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>
