From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luke.yx.lee@gmail.com, juri@linkov.net, emacs-devel@gnu.org
Subject: Re: [ELPA] Brief v5.90: neighboring window merge on deletion
Date: Wed, 27 Mar 2024 08:35:04 +0100 [thread overview]
Message-ID: <83e69e6f-3b2e-4488-adb3-98dd3ea5556f@gmx.at> (raw)
In-Reply-To: <864jctjgw8.fsf@gnu.org>
>> IIUC handling overlays with a 'window' property with current means is
>> much too cumbersome. One would have to investigate all overlays in the
>> window's buffer and duplicate them if they have a 'window' property that
>> references the cloned window. In practice, most overlays don't have
>> such a property.
>
> But crucially, the overlay that implements region highlighting does.
This, cursor face highlighting and rectangle overlays are special. They
change with the selected window, the region and/or the position of point
and must be regenerated in every redisplay cycle anyway. Which means
that they need no special attention when cloning a frame or window
configuration. Others, like the one used by 'hl-line-mode' are handled
via a post command hook and probably need no special attention either.
The overlays used by 'compare-windows-highlight' or
'isearch-lazy-highlight-match' seem more sensitive in this regard. I
doubt that they would survive a change where windows do not preserve
their identity.
martin
next prev parent reply other threads:[~2024-03-27 7:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:23 [ELPA] Brief v5.90: neighboring window merge on deletion 路客
2024-03-22 13:22 ` Emanuel Berg
2024-03-23 18:33 ` Juri Linkov
2024-03-24 5:13 ` 路客
2024-03-24 9:54 ` martin rudalics
2024-03-24 15:51 ` 路客
2024-03-25 9:40 ` martin rudalics
2024-03-26 2:31 ` 路客
2024-03-26 9:57 ` martin rudalics
2024-03-26 12:51 ` Eli Zaretskii
2024-03-27 7:35 ` martin rudalics [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-24 3:25 路客
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=83e69e6f-3b2e-4488-adb3-98dd3ea5556f@gmx.at \
--to=rudalics@gmx.at \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=luke.yx.lee@gmail.com \
/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).