unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: <miha@kamnitnik.top>
Cc: 58176@debbugs.gnu.org
Subject: bug#58176: 29.0.50; mouse-set-point region flicker with highlight-nonselected-windows=t and same buffer in two windows
Date: Fri, 30 Sep 2022 08:45:44 +0300	[thread overview]
Message-ID: <835yh5fm9j.fsf@gnu.org> (raw)
In-Reply-To: <87wn9lubu6.fsf@miha-pc>

> From: <miha@kamnitnik.top>
> Cc: 58176@debbugs.gnu.org
> Date: Thu, 29 Sep 2022 23:09:37 +0200
> 
> > It's a direct consequence of the fact that point is different in each
> > window.  I don't see any bug here, FWIW.  If you don't like this side
> > effect of highlight-nonselected-windows, then don't set it non-nil.
> 
> Well, maybe we could try a bit harder to reduce the flicker for ordinary
> non-dragging mouse-1 clicks. One idea could be to prevent down-mouse-1
> from activating mark until the region becomes non-zero length, so
> something like this patch.

Thanks, but this is exactly the opposite of the behavior we want.  We
currently make a significant effort to show regions of zero length.





  reply	other threads:[~2022-09-30  5:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 17:38 bug#58176: 29.0.50; mouse-set-point region flicker with highlight-nonselected-windows=t and same buffer in two windows miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-29 18:54 ` Eli Zaretskii
2022-09-29 21:09   ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-30  5:45     ` Eli Zaretskii [this message]
2022-09-30 21:15       ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-01  5:38         ` Eli Zaretskii
2022-10-01 10:00           ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-01  9:58             ` Eli Zaretskii

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=835yh5fm9j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58176@debbugs.gnu.org \
    --cc=miha@kamnitnik.top \
    /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).