unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Matt Armstrong <matt@rfc20.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 58479@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	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 22:56:47 -0700	[thread overview]
Message-ID: <8735bnc7s0.fsf@rfc20.org> (raw)
In-Reply-To: <874jw3jl13.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> Matt Armstrong <matt@rfc20.org> writes:
>
>>> 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.
>
> You can download it and open locally.
> Also, do note that the second issue was present _before_ Stefan's patch.
> Then, Stefan expressed a concern that even though the patch fixed
> immediate problem, it might be creating other issues are he did not
> anticipate the patch to make any difference in the output of
> describe-text-properties (AFAIU).

Okay, I'm able to watch your video and think I see what you're talking
about there, but I am not able to reproduce a problem with the Stefan's
fix applied.  Maybe there is some miscommunication.  Everything I try
now seems to work the same on master and the most recent
feature/noverlay.  Could you start from the beginning and provide steps?
I am a little lost with "press this after third step of that after
watching video."  :-)

The "Hello, World" string was a little confusing.  Here is a simpler
version:

(defun my-b58479-3 ()
  (interactive)
  (with-current-buffer (get-buffer-create "*b58479*")
    (add-to-invisibility-spec (cons 'ellipsis t))
    (erase-buffer)
    (delete-all-overlays)
    (insert "123456789")
    (let ((overlay (make-overlay 2 9)))
      (overlay-put overlay 'invisible 'ellipsis))
    (display-buffer (current-buffer))))

Looks like `describe-text-properties' first tries `overlays-at' and,
finding nothing, will try (overlays-in (point) (1+ (point))) to get the
zero-width overlays.

-- 
matt (sent from an Emacs running the feature/noverlay branch)





  reply	other threads:[~2022-10-17  5:56 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
2022-10-17  1:28                   ` Ihor Radchenko
2022-10-17  5:56                     ` Matt Armstrong [this message]
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=8735bnc7s0.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).