From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 56662@debbugs.gnu.org, visuweshm@gmail.com
Subject: bug#56662: 29.0.50; Funny region highlights when highlight-nonselected-windows is t
Date: Thu, 21 Jul 2022 09:22:01 +0300 [thread overview]
Message-ID: <83lesnnfxy.fsf@gnu.org> (raw)
In-Reply-To: <871qufpmjp.fsf@gmail.com> (message from Kévin Le Gouguec on Wed, 20 Jul 2022 22:16:26 +0200)
> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: Visuwesh <visuweshm@gmail.com>, 56662@debbugs.gnu.org
> Date: Wed, 20 Jul 2022 22:16:26 +0200
>
> (1) Haven't been able to find a reproducible recipe, but on occasion,
> when hitting C-SPC in window-2, the highlighting in window-1
> sometimes "snaps" and updates to match the mark I just set in
> window-2.
Probably because you did something that deactivated the mark there.
It's very easy to deactivate the mark. Which is why this feature is
only good for very short periods of time, and shouldn't be expected to
DTRT in any scenario except temporarily having more than one window
with highlight -- unless you never display the same buffer in several
windows.
> I kind of wish there was a third value for this user option;
> e.g. (setq highlight-nonselected-windows 'lazy) to signify "keep
> highlighting as-is when leaving the window, and never update it
> until the window becomes current again"? 🤷
How would that work, if you take into consideration that the region is
between the mark and point?
And again, are you talking about the same buffer displayed in several
windows, or are you talking about different buffers? For the latter
case, I think the problems you describe don't exist.
> If any of (2) makes sense, could this bug remain open as a wishlist
> item?
I don't see how it could work, but maybe I'm missing something.
In any case, does someone volunteer to work on this? Because if not,
we'll just have another bug report that is open forever.
next prev parent reply other threads:[~2022-07-21 6:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 11:35 bug#56662: 29.0.50; Funny region highlights when highlight-nonselected-windows is t Visuwesh
2022-07-20 12:38 ` Eli Zaretskii
2022-07-20 12:43 ` Visuwesh
2022-07-20 12:48 ` Eli Zaretskii
2022-07-20 20:16 ` Kévin Le Gouguec
2022-07-21 6:22 ` Eli Zaretskii [this message]
2022-07-21 11:22 ` Visuwesh
2022-07-21 12:19 ` Eli Zaretskii
2022-07-21 12:32 ` Visuwesh
2022-07-21 12:39 ` Eli Zaretskii
2022-07-21 14:35 ` Visuwesh
2022-07-21 15:54 ` Eli Zaretskii
2022-07-21 16:13 ` Visuwesh
2022-07-21 16:34 ` Eli Zaretskii
2022-07-21 17:00 ` Visuwesh
2022-07-21 22:14 ` Kévin Le Gouguec
2022-07-24 16:41 ` Juri Linkov
2022-07-24 17:32 ` Eli Zaretskii
2022-07-23 7:09 ` Lars Ingebrigtsen
2022-07-23 7:08 ` Lars Ingebrigtsen
2022-07-20 18:05 ` Juri Linkov
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=83lesnnfxy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56662@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=visuweshm@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).