unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 56662@debbugs.gnu.org
Subject: bug#56662: 29.0.50; Funny region highlights when highlight-nonselected-windows is t
Date: Fri, 22 Jul 2022 00:14:30 +0200	[thread overview]
Message-ID: <87y1wm9kqh.fsf@gmail.com> (raw)
In-Reply-To: <87sfmupfj6.fsf@gmail.com> (Visuwesh's message of "Thu, 21 Jul 2022 22:30:13 +0530")

Visuwesh <visuweshm@gmail.com> writes:

>> If you deactivate the mark, there's no region, so I'm not sure why
>> you want to see highlighting in that case.
>
> OK, I see the full picture now, now that I re-read your reply to Kevin.
> If you change the mark in window B, then the region highlighting will be
> different from that of window A.  But currently there's no way to make
> window A highlight the region whilst having no region highlight in
> window B unless the point and the mark is the same in window B.  I hope
> I am right.  I think this is what Kevin (and I) want IIUC.

Right.  Paraphrasing my message, I like to keep useful snippets
highlighted in one window while working in another; it's frustrating to
have this break down just because both windows happen to display the
same buffer.

>> Are we talking about the Emacs region highlighting, or are we talking
>> about some other highlighting?  As the manual explains, the Emacs
>> selection highlighting is different from other applications in several
>> important ways.
>
> We are talking about Emacs region highlighting, and yes I do understand
> the difference between Emacs and other applications.
>
> In any case, I don't think there's any reasonable action we can take.
> "Active region" is already bending Emacs quite a bit, the current
> scenario seems to break the camel's hump in unexpected ways (altho
> there's always a reason to explain the behaviour).  Closing the bug
> report.

That's fair.  My argument for keeping it open would be that people who
would be able and willing to scratch that itch in the future might not
think to search for closed reports; but then again I suppose there's not
a lot of information in our present discussion that they wouldn't be
able to rediscover on their own.

Thanks for reporting this nonetheless; if anything, seeing someone else
bothered by the current behaviour was mildly cathartic.





  reply	other threads:[~2022-07-21 22:14 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
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 [this message]
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=87y1wm9kqh.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=56662@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).