bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing

[Matt Armstrong <matt@rfc20.org>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Ihor Radchenko [2022-10-19 08:09:32] wrote:
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>> After executing 3, if I run M-x describe-text-properties, the overlay is
>>>> not listed in the text properties. Running
>>>> M-: (overlays-in (point-min) (point-max)) does list the 0-length
>>>> overlay 5..5. However, running M-: (overlays-at 5) yields nil.
>>>
>>> I don't see this here: the overlay is listed just as much after as
>>> before the patch.  Are you sure you were calling
>>> `M-x describe-text-properties` exactly from the same buffer position?
>>
>> I feel confused.
>> Didn't you tell me that 0-length overlays should not be listed by
>> describe-text-properties?
>
> I can't remember saying such a thing, no, unless I was myself confused.
> It probably doesn't matter now, tho: let's mark this up to a big
> confusion/miscommunication and move on :-)

I think this is where the confusion started:

>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
> That is very strange and makes me suspect there's something I'm maybe
> misunderstanding in the code I changed.

...and then you asked for a way to reproduce it.  I think we're clear on
the issue now, though.  Turns out this "very strange" behavior is
perhaps still strange, but at least the same on master and
feature/noverlay, at least I think!