From: Visuwesh <visuweshm@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: David Ponce <da_vid@orange.fr>,
Lars Ingebrigtsen <larsi@gnus.org>,
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 17:05:24 +0530 [thread overview]
Message-ID: <87bkttkzyb.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkmn+6-pTNnaifS4PVLndT5_vOjXWDhFzYStRZFJLLhanTA@mail.gmail.com> (Stefan Kangas's message of "Wed, 13 Jul 2022 04:30:19 -0700")
[Wednesday July 13, 2022] Stefan Kangas wrote:
> Visuwesh <visuweshm@gmail.com> writes:
>
>> AFAICT, the recipe produces what I had in my mind when I proposed. The
>> behaviour might seems slightly odd since mouse-yank-at-point is set to
>> nil in OP's case. It shouldn't be hard to take this defcustom into
>> account tho.
>
> I think that neither Emacs nor `cua-mode' should behave differently from
> other X programs in this regard, certainly not by default. Could we
> please avoid that? The entire point of `cua-mode' is to be /more/ like
> other software, not less.
Like I said in the original bug report, I have no problems if the change
was reverted. I would do it myself but I have no push access.
next prev parent reply other threads:[~2022-07-13 11:35 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 [this message]
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
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=87bkttkzyb.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=56530@debbugs.gnu.org \
--cc=da_vid@orange.fr \
--cc=larsi@gnus.org \
--cc=stefankangas@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).