GNU bug report logs -
#14582
24.3.50.1; Strange overlay behavior, when window-start is inside an overlay.
Previous Next
Full log
Message #67 received at 14582 <at> debbugs.gnu.org (full text, mbox):
> Date: Wed, 02 Feb 2022 14:31:35 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: larsi <at> gnus.org, esabof <at> gmail.com, 14582 <at> debbugs.gnu.org
>
> > From: Michael Heerdegen <michael_heerdegen <at> web.de>
> > Cc: larsi <at> gnus.org, esabof <at> gmail.com, 14582 <at> debbugs.gnu.org
> > Date: Wed, 02 Feb 2022 05:02:41 +0100
> >
> > Is there a third alternative, a hook or something that could be used, to
> > perform this task automatically?
>
> It cannot be a hook, because from the display engine POV nothing
> happened that could trigger a hook. The visible contents of the
> window is different, that's all.
>
> So it shouldn't be a hook, it should be a buffer-local variable that
> would change how redisplay behaves in these cases. I will see what
> can be done about it.
I installed a change along these lines. A buffer that sets the new
variable make-window-start-visible non-nil should force redisplay to
reject a window-start point that is in invisible text or is covered by
a "replacing" 'display' property (which also makes window-start
invisible), and choose a different starting point.
Please test.
This bug report was last modified 3 years and 75 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.