Ilya Chernyshov writes: > Preserved old behavior for `org-element-timestamp-interpreter' > function for :range-type set to `nil'. The new function > > The new function takes into account :range-type value when interpreting > ranges and throws error when :range-type set for `active'/`inactive' > types. Thanks! The patch looks good in general, but there is at least one test failing when I run make test. May you please check? Also, see the attached diff where I suggest some comments to explain the code logic.