From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56662@debbugs.gnu.org
Subject: bug#56662: 29.0.50; Funny region highlights when highlight-nonselected-windows is t
Date: Wed, 20 Jul 2022 18:13:16 +0530 [thread overview]
Message-ID: <877d48550b.fsf@gmail.com> (raw)
In-Reply-To: <83wnc8klhw.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 20 Jul 2022 15:38:03 +0300")
[புதன் ஜூலை 20, 2022] Eli Zaretskii wrote:
>> From: Visuwesh <visuweshm@gmail.com>
>> Date: Wed, 20 Jul 2022 17:05:11 +0530
>>
>> 1. emacs -Q
>> 2. Visit a longish file.
>> 3. C-x 3 and scroll up in any of the window.
>> 4. M-: (setq highlight-nonselected-windows t) RET.
>> 5. Create an active region and compare the highlighting.
>
> What is wrong with this behavior? In each window the region between
> the mark and point is highlighted, as you requested by turning on that
> option.
>
> What am I missing?
Since the point is local to the window, it felt natural that the region
would be too. But since the region simply highlights the text between
the point and the mark, the current behaviour is not strange indeed. I
guess there's nothing to do here and this bug can be closed?
next prev parent reply other threads:[~2022-07-20 12:43 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 [this message]
2022-07-20 12:48 ` Eli Zaretskii
2022-07-20 20:16 ` Kévin Le Gouguec
2022-07-21 6:22 ` Eli Zaretskii
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=877d48550b.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=56662@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).