From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56662@debbugs.gnu.org, kevin.legouguec@gmail.com
Subject: bug#56662: 29.0.50; Funny region highlights when highlight-nonselected-windows is t
Date: Thu, 21 Jul 2022 20:05:58 +0530 [thread overview]
Message-ID: <875yjqr0s1.fsf@gmail.com> (raw)
In-Reply-To: <83wnc6mygg.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Jul 2022 15:39:43 +0300")
[வியாழன் ஜூலை 21, 2022] Eli Zaretskii wrote:
>> >> I can think of one way this could potentially work is by checking if the
>> >> mark was made when window was active so making the mark "window-aware"?
>> >> I.e., if two windows A and B show the same buffer and the user typed
>> >> C-SPC when in window A, then the region would not show up in window B.
>> >> Does this make sense?
>> >
>> > So what happens if the user then types "C-x o" to switch to B?
>>
>> Ideally, nothing. Only the active window changes but the region
>> highlighting before and after should be the same.
>
> But that's a bug: region highlighting should definitely work in a
> selected window.
>
It won't be a bug if the region is considered window-local.
"Window-local" because the region was made when in window A and so its
"active"-ness is confined to window A.
>> Here's another question: what about delete-selection-mode when the
>> active window is B?
>
> What about it?
If we were to make the region window-local, then should
delete-selection-mode delete the region when in window B?
next prev parent reply other threads:[~2022-07-21 14:35 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
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 [this message]
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=875yjqr0s1.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=56662@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kevin.legouguec@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).