I applied your patch and yet I saw no difference in behavior. I was still not able to move the point into the timestamp. I will admit that the editing experience in the minibuffer is very unintuitive. But I don't think the intent is to give users the chance to directly change the timestamp. Instead, you are supposed to create a new timestamp which will replace the old one that you are currently editing.
I used the following test file: #+begin_src org #+STARTUP: customtime * TODO H SCHEDULED: <2020-03-29 Thu .+1d> #+end_src Am I missing something? Also overlays and text-properties are not the same thing. The code you provided will only strip text-properties. If overlays are what you are trying to change, you should take a look at `org-read-date-display'. Le lun. 2 nov. 2026 à 05:59, Earl Chase <[email protected]> a écrit : > > Owned. > > I will take a look at this. > > Le lun. 2 nov. 2026 à 03:46, Marten Lienen <[email protected]> a écrit : > > > > Hello, > > > > This patch strips the text properties from the timestamp, so that the text > > overlay from `org-display-custom-times' does not appear in the minibuffer > > when editing a timestamp. On the one hand, this overlay is quite large and > > takes a lot of space in the minibuffer and on the other hand, it is > > impossible to move point into it to edit it, which makes the editing > > experience unintuitive. > > > > Best, > > Marten
