> but please send this patch to the bug-gnu-emacs list instead so
> that we don't lose track of it.

I have sent the patch to bug-gnu-emacs@gnu.org but I can't receive any response which should be something like bug#xxx. I have subscribed to bug-gnu-emacs and can receive other people's bug mail.

To make tracking easier (e.g. other people may use archive to search in the future), I repeated the email title: "[PATCH] Fix C-x C-c do not work in CUA-mode when cua-prefix-override-handler is ni" and added the patch attachment here. This patch (0001-Fix-the-issue-when-cua-prefix-override-handler-is-ni.patch) works in Emacs 29.3.

Note that the patch I provided previously on May 24, 2024 only works in Emacs 28.2 (newer cua-base.el has some changes). Also, there is a typo in the previous patch that I forgot to call `call-interactively` to `kill-region` and `copy-region-as-kill`.

So if someone uses Emacs 29.3 or newer build, please use this patch I just attached or the patch I sent to bug-gnu-emacs in which the typo has been also fixed.

Best regards,

Siyuan Chen

On Mon, May 27, 2024 at 6:20 PM Siyuan Chen <chansey97@gmail.com> wrote:

Dear Eli,

> I think this is a documentation issue.
>
> When cua-prefix-override-inhibit-delay is nil, the prefix is never
> overridden, i.e. "C-x" will never delete the marked text.

The real problem is that if we have to set `cua-prefix-override-inhibit-delay` non-nil, or setting `cua-prefix-override-inhibit-delay` nil means "C-x" never delete the marked text, then the CUA-mode will not be able to support fast copy/cut & paste as I said in the original post.

> I added Kim to the discussion, in the hope that he could shed some
light on the intended behavior.

That's great.

Dear Stefan,

> but please send this patch to the bug-gnu-emacs list instead so
that we don't lose track of it.

OK. I will send it later.

On Sun, May 26, 2024 at 1:35 AM Stefan Kangas <stefankangas@gmail.com> wrote:
Siyuan Chen <chansey97@gmail.com> writes:

> Use the following patch instead

Thanks, but please send this patch to the bug-gnu-emacs list instead so
that we don't lose track of it.

It would be best if you could send your patch as an attachment, as the
result of running the command `git format-patch -1`.