From: David Ponce <da_vid@orange.fr>
To: Visuwesh <visuweshm@gmail.com>
Cc: 56530@debbugs.gnu.org
Subject: bug#56530: 29.0.50; mouse-2 cut selected text when cua-mode is enabled
Date: Wed, 13 Jul 2022 13:10:32 +0200 [thread overview]
Message-ID: <a0d569df-37d4-bcbe-3231-b0926193527e@orange.fr> (raw)
In-Reply-To: <877d4hmjdh.fsf@gmail.com>
On 13/07/2022 11:50, Visuwesh wrote:
> [Wednesday July 13, 2022] David Ponce wrote:
>
>> Hello,
>>
>> I noticed that now, when cua-mode is enabled, when I select a region
>> (with mouse or keyboard), then use mouse-2 click on another point to
>> insert the selected text, the active region is cut before to insert text
>> at the mouse-2 click for the first time. As far as I remember this is a
>> new behavior, and previously the selected region was not cut, but
>> copied, like when cua-mode is disabled.
>>
>> The woraround is to first deselect the region before to click mouse-2 to
>> insert the previously selected text. This way the initially selected
>> text is not cut.
>>
>> Not sure this is expected, so this bug report ;-)
>
> It is expected. mouse-2 (and other mouse yank commands) were recently
> changed to respect delete-selection-mode (which is enabled by cua-mode)
> by yours truly. :-)
>
> You can disable the new behaviour by saying,
>
> (put 'mouse-yank-primary 'delete-selection nil)
> (put 'mouse-yank-secondary 'delete-selection nil)
> (put 'mouse-yank-at-click 'delete-selection nil)
>
> But I guess, it sure didn't take long for the complaints to come in
Maybe the behavior could be disabled for cua-mode to be consistent with
CUA expected behavior? After all, cua-mode is more than just
delete-selection-mode ;-)
Thanks
[resent, forgot to CC the bug list]
next prev parent reply other threads:[~2022-07-13 11:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 9:22 bug#56530: 29.0.50; mouse-2 cut selected text when cua-mode is enabled David Ponce
2022-07-13 9:50 ` Visuwesh
2022-07-13 10:19 ` Lars Ingebrigtsen
2022-07-13 11:03 ` Visuwesh
2022-07-13 11:11 ` Lars Ingebrigtsen
2022-07-13 11:19 ` Visuwesh
2022-07-13 11:40 ` Lars Ingebrigtsen
2022-07-13 11:30 ` Stefan Kangas
2022-07-13 11:35 ` Visuwesh
2022-07-13 19:14 ` Juri Linkov
2022-07-13 19:19 ` Juri Linkov
2022-07-14 17:20 ` Lars Ingebrigtsen
2022-07-14 17:24 ` Juri Linkov
2022-07-14 18:04 ` Lars Ingebrigtsen
2022-07-15 18:53 ` Juri Linkov
2022-07-16 10:34 ` Lars Ingebrigtsen
2022-07-17 18:49 ` Juri Linkov
2022-07-22 15:07 ` Lars Ingebrigtsen
2022-07-24 16:52 ` Juri Linkov
2022-07-26 12:08 ` Lars Ingebrigtsen
2022-07-13 11:10 ` David Ponce [this message]
2022-07-13 11:16 ` Visuwesh
2022-07-14 0:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 10:10 ` Stefan Kangas
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=a0d569df-37d4-bcbe-3231-b0926193527e@orange.fr \
--to=da_vid@orange.fr \
--cc=56530@debbugs.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).