From: Matt Armstrong <matt@rfc20.org>
To: Ihor Radchenko <yantar92@posteo.net>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 58479@debbugs.gnu.org, Ihor Radchenko <yantar92@gmail.com>
Subject: bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing
Date: Sun, 16 Oct 2022 16:41:41 -0700 [thread overview]
Message-ID: <87czarcp56.fsf@rfc20.org> (raw)
In-Reply-To: <87a65xqi8d.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> I was confused because zero-length overlays were listed by
>>> describe-text-properties before your patch above.
>>
>> That is very strange and makes me suspect there's something I'm maybe
>> misunderstanding in the code I changed.
>> Can you send a recipe that shows this difference?
>
> See the recorded video link. Basically, I just executed M-x
> describe-text-properties after (3) in my second recipe.
Ihor, I can't reproduce this second issue. I can't see your video.
Firefox on Debian Testing can't decode it for some reason.
Based on your description I wrote this. Please excuse any amateurish
elisp.
(with-current-buffer (get-buffer-create "*b58479-2*")
(delete-all-overlays)
(erase-buffer)
(insert "Empty overlay here: --><--\n")
(goto-char (point-min))
(search-forward "<")
(let* ((pos (point))
(overlays-at `(overlays-at ,pos))
(describe-text-properties
`(describe-text-properties
,pos (current-buffer) (current-buffer))))
(make-overlay (point) (point))
(next-line)
(insert (format "%S -> %S\n"
overlays-at (eval overlays-at)))
(insert (format "%S follows:\n" describe-text-properties))
(eval describe-text-properties))
(display-buffer (current-buffer)))
On mainline, I get this buffer:
----------------------------------------------------------------------
Empty overlay here: --><--
(overlays-at 25) -> nil
(describe-text-properties 25 (current-buffer) (current-buffer)) follows:
There is an overlay here:
From 25 to 25
----------------------------------------------------------------------
On the noverlay branch I get the same result.
next prev parent reply other threads:[~2022-10-16 23:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 2:17 bug#58479: 29.0.50; [feature/noverlay] Displaced overlays in notmuch search buffers after refreshing Ihor Radchenko
2022-10-13 4:25 ` Matt Armstrong
2022-10-14 4:56 ` Ihor Radchenko
2022-10-14 20:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 1:38 ` Ihor Radchenko
2022-10-15 3:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 4:11 ` Ihor Radchenko
2022-10-15 13:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 14:22 ` Ihor Radchenko
2022-10-16 23:41 ` Matt Armstrong [this message]
2022-10-17 1:28 ` Ihor Radchenko
2022-10-17 5:56 ` Matt Armstrong
2022-10-17 8:21 ` Ihor Radchenko
2022-10-17 18:53 ` Matt Armstrong
2022-10-17 22:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 20:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-19 8:09 ` Ihor Radchenko
2022-10-19 12:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-19 21:59 ` Matt Armstrong
2022-10-19 22:26 ` Matt Armstrong
2022-10-19 23:49 ` Matt Armstrong
2022-10-20 1:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-20 21:59 ` Matt Armstrong
2022-10-20 22:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czarcp56.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=58479@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@gmail.com \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).