From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#58176: 29.0.50; mouse-set-point region flicker with highlight-nonselected-windows=t and same buffer in two windows Date: Sat, 01 Oct 2022 08:38:01 +0300 Message-ID: <83czbccddy.fsf@gnu.org> References: <86pmfeaxnv.fsf@miha-pc> <838rm2f1v8.fsf@gnu.org> <87wn9lubu6.fsf@miha-pc> <835yh5fm9j.fsf@gnu.org> <87h70otvgs.fsf@miha-pc> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3419"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 58176@debbugs.gnu.org To: Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 01 07:39:17 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oeVDY-0000fC-QJ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 01 Oct 2022 07:39:16 +0200 Original-Received: from localhost ([::1]:42028 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oeVDX-000698-CC for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 01 Oct 2022 01:39:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38086) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeVDK-00063D-Mu for bug-gnu-emacs@gnu.org; Sat, 01 Oct 2022 01:39:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44360) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oeVDK-0007TT-ES for bug-gnu-emacs@gnu.org; Sat, 01 Oct 2022 01:39:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oeVDK-0000z4-5l for bug-gnu-emacs@gnu.org; Sat, 01 Oct 2022 01:39:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 01 Oct 2022 05:39:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58176 X-GNU-PR-Package: emacs Original-Received: via spool by 58176-submit@debbugs.gnu.org id=B58176.16646027013734 (code B ref 58176); Sat, 01 Oct 2022 05:39:02 +0000 Original-Received: (at 58176) by debbugs.gnu.org; 1 Oct 2022 05:38:21 +0000 Original-Received: from localhost ([127.0.0.1]:43438 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oeVCf-0000y9-AM for submit@debbugs.gnu.org; Sat, 01 Oct 2022 01:38:21 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:41984) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oeVCc-0000xv-Q4 for 58176@debbugs.gnu.org; Sat, 01 Oct 2022 01:38:19 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55712) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeVCX-0007Qj-1T; Sat, 01 Oct 2022 01:38:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=qEtbhbnMO9WYEjMj8zR8QXtSVFGmR37uwwqbgM/QN50=; b=IG9nhNAqOP7M 8ElF6jZkdt78iPXg75ellJBbtRAqXbnqLpVlLBOEJhr5alMYVui6B3GurQztYSTdRSk2SQmVJZtiH BkLRDVDZ/lnqrkDGLPyVC7hqtYzl3VzEt5/YStPCAJ76uHHAVEi5EDFtGLoHWgB/s1u8YVuhvvVVh +2b1F0DGjz8mLzqeHhgpCTB87HYESNpc6fAOAkiRQNvGhJHCXswgpaVI54Bt81yWx6UBAGFxMfH+3 16yJGiVt2qW4DuT4HdnuNIyMAOlCBVIjzLou/3s4Mp/g6oYjJxbDxNlvrp/QT3DiFzt1G4s34xfmI ngdpGq9pG1kR95KGDK2gfg==; Original-Received: from [87.69.77.57] (port=4912 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeVCW-0002Gp-BW; Sat, 01 Oct 2022 01:38:12 -0400 In-Reply-To: <87h70otvgs.fsf@miha-pc> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:244074 Archived-At: > From: > Cc: 58176@debbugs.gnu.org > Date: Fri, 30 Sep 2022 23:15:31 +0200 > > >> 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. > > (I'm assuming that by "show regions of zero length", you mean that the > "Copy text" toolbar icon is enabled.) No, we actually attempt to display zero-length regions in the text. > I hope I'm not arguing semantics too much, but my patch doesn't actually > hide an (active) region of zero length, it prevents one from being > activated. Which is against the behavior we want, I think. > It only prevents it in the specific case of a non-dragging mouse-1 > click, which makes quite a lot sense to me. The current behaviour of a > non-dragging mouse-1 click is that the zero-length region is only active > for the duration of the mouse button being held down. Once the button is > released, the zero-length region is deactivated, which makes it not very > useful, as far as I can see. It is useful in the much more frequent use case where the user then drags the mouse. > If you want to create a zero-length region that stays active after > releasing mouse-1, you have to drag the mouse a little first to make the > region length non-zero and then drag the mouse back to the starting > position to make the region length zero again. This use case is still > supported by my patch. > > (Perhaps I missed some use-cases of a zero-length region active during a > non-dragging mouse-1 button hold. If you know any, please let me know > about them.) > > This, together with the fact that it reduces the "flicker" from the > original message, makes me insist on the patch. I still insist that what you propose is the opposite of the behavior we want.