unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: "Eli Zaretskii" <eliz@gnu.org>,
	56662@debbugs.gnu.org,
	"Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Subject: bug#56662: 29.0.50; Funny region highlights when highlight-nonselected-windows is t
Date: Sat, 23 Jul 2022 09:08:07 +0200	[thread overview]
Message-ID: <87czdw5mso.fsf@gnus.org> (raw)
In-Reply-To: <87h73a7lsx.fsf@gmail.com> (Visuwesh's message of "Thu, 21 Jul 2022 16:52:06 +0530")

Visuwesh <visuweshm@gmail.com> writes:

> 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?  But I'm not sure if this heuristic will work at
> all times as it bends the notion of "active region" way too much.

I think what you're asking for here is really to make the mark a window
entity instead of a buffer thing.  (The point can be specified per
window, but the mark can't.)

I think that sounds like an interesting feature (and would allow having
different highlighted regions in different windows displaying the same
buffer), but sounds like it would be very backwards-incompatible.

I've also been annoyed by how showing the same buffer in two windows
isn't more...  "separate".  When editing two different sections of the
same buffer at the same time, it's really easy to get pretty confused
(especially when jumping to the mark with `C-x C-x').






  parent reply	other threads:[~2022-07-23  7:08 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
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 [this message]
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=87czdw5mso.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56662@debbugs.gnu.org \
    --cc=eliz@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).