From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#32747: 26; `C-M-w M-w' with non-nil `mouse-drag-copy-region', if selected with mouse Date: Wed, 19 Sep 2018 21:44:25 +0300 Message-ID: <83o9cte392.fsf@gnu.org> References: <<>> <<<83tvmlew2a.fsf@gnu.org>>> <<932a1915-c043-4708-9f16-dc0ee8fafdb3@default>> <<83pnx9een5.fsf@gnu.org>> <01b0f0c4-e3b8-440f-a739-5995ca4ff615@default> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1537382628 31113 195.159.176.226 (19 Sep 2018 18:43:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 19 Sep 2018 18:43:48 +0000 (UTC) Cc: 32747@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Sep 19 20:43:44 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g2hRt-0007uc-IH for geb-bug-gnu-emacs@m.gmane.org; Wed, 19 Sep 2018 20:43:41 +0200 Original-Received: from localhost ([::1]:46787 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g2hU0-0004Rv-87 for geb-bug-gnu-emacs@m.gmane.org; Wed, 19 Sep 2018 14:45:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g2hTK-00043O-TH for bug-gnu-emacs@gnu.org; Wed, 19 Sep 2018 14:45:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g2hTF-0004pF-Q6 for bug-gnu-emacs@gnu.org; Wed, 19 Sep 2018 14:45:09 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:41717) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g2hTC-0004lr-Rq for bug-gnu-emacs@gnu.org; Wed, 19 Sep 2018 14:45:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g2hTC-00044d-CB for bug-gnu-emacs@gnu.org; Wed, 19 Sep 2018 14:45: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: Wed, 19 Sep 2018 18:45:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32747 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32747-submit@debbugs.gnu.org id=B32747.153738269315623 (code B ref 32747); Wed, 19 Sep 2018 18:45:02 +0000 Original-Received: (at 32747) by debbugs.gnu.org; 19 Sep 2018 18:44:53 +0000 Original-Received: from localhost ([127.0.0.1]:45975 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g2hT3-00043v-7b for submit@debbugs.gnu.org; Wed, 19 Sep 2018 14:44:53 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:43706) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g2hT1-00043h-VO for 32747@debbugs.gnu.org; Wed, 19 Sep 2018 14:44:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g2hSt-0004N1-8i for 32747@debbugs.gnu.org; Wed, 19 Sep 2018 14:44:46 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47558) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g2hSt-0004MR-0s; Wed, 19 Sep 2018 14:44:43 -0400 Original-Received: from [176.228.60.248] (port=4615 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1g2hSr-0002ln-4a; Wed, 19 Sep 2018 14:44:42 -0400 In-reply-to: <01b0f0c4-e3b8-440f-a739-5995ca4ff615@default> (message from Drew Adams on Wed, 19 Sep 2018 11:24:50 -0700 (PDT)) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:150458 Archived-At: > Date: Wed, 19 Sep 2018 11:24:50 -0700 (PDT) > From: Drew Adams > Cc: 32747@debbugs.gnu.org > > > > Anyay, replaying the recipe now (again, from -Q), I see the bad > > > behavior in _all_ Emacs releases (including back to Emacs 20, > > > when there was no variable `mouse-drag-copy-region'). > > > > Makes sense, because those versions worked as if > > mouse-drag-copy-region was t. Emacs 22.1 added that variable, and you > > should be able to see the problem go away starting from that version, > > when this variable is nil. > > No. As I said, I checked Emacs 22.3.1 - to be exact: > > GNU Emacs 22.3.1 (i386-mingw-nt6.2.9200) of 2008-09-06 on SOFT-MJASON I just tried that version, and I still see that mouse-drag-copy-region changes the behavior. > I've checked it multiple times now, each time from `emacs -Q'. > This is my Emacs 23.4 version: > GNU Emacs 23.4.1 (i386-mingw-nt6.2.9200) of 2012-02-04 on MARVIN > > And I see the same thing in subsequent releases, as I said. > I'm on Windows 10. Nothing special about my Windows, AFAIK. I'm on XP, but that's where the difference ends. I have no idea why you see a different behavior, and I don't have Windows 10 nearby to check what happens there. > > Indeed, with that variable non-nil, users are not expected to copy and > > paste using the keyboard, they are expected to do that with the mouse. > > And they certainly aren't expected to mix both methods in the same > > sequence of actions on the same text. > > I don't agree. Nothing in the description of `mouse-drag-copy-region' > suggests that with a non-nil value users are not expected to also > copy and paste using the keyboard. That would make no sense. You can do both, but when you mix them, you get 2 copies of each kill/copy in the kill-ring. > There is no reason that someone should not be able to use `C-M-w' > to affect copies/kills made with the mouse. And there is nothing in > the doc to suggest otherwise. This behavior was never implemented. If that is what you want, you are asking for a new feature, not reporting a bug, let alone a regression.