[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch sea
From: |
Stefan Monnier |
Subject: |
bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing |
Date: |
Fri, 14 Oct 2022 23:52:44 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
> However, I noticed a different problem introduced by the patch.
Are you sure? The patch should now affect `overlays-at` at all
(actually, one of the reasons for the introduction of the bug fixed by
the patch is because that code path for `get-char-property` does not
rely on the same code path as `overlays-at`. The old code shared the
code path for those two, but the new code tries to be more efficient by
avoiding allocation for a temporary storage and reducing an O(N log N)
to O(N)))).
> 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 think that the above is not right.
Whether this is "right" or not is a good question, but AFAIK it's the
"expected" behavior in the sense that it's how `overlays-at` has worked
until now. So I think it's "right".
Stefan
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Ihor Radchenko, 2022/10/12
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Matt Armstrong, 2022/10/13
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Ihor Radchenko, 2022/10/14
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Stefan Monnier, 2022/10/14
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Ihor Radchenko, 2022/10/14
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing,
Stefan Monnier <=
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Ihor Radchenko, 2022/10/15
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Stefan Monnier, 2022/10/15
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Ihor Radchenko, 2022/10/15
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Matt Armstrong, 2022/10/16
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Ihor Radchenko, 2022/10/16
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Matt Armstrong, 2022/10/17
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Ihor Radchenko, 2022/10/17
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Matt Armstrong, 2022/10/17
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Stefan Monnier, 2022/10/17
- bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing, Stefan Monnier, 2022/10/18