From: Stefan Kangas <stefankangas@gmail.com>
To: Shynur Xie <one.last.kiss@outlook.com>
Cc: Po Lu <luangruo@yahoo.com>,
"63872@debbugs.gnu.org" <63872@debbugs.gnu.org>
Subject: bug#63872: [PATCH] `mouse-drag-and-drop-region' sometimes couldn't cut
Date: Wed, 6 Sep 2023 03:57:46 -0700 [thread overview]
Message-ID: <CADwFkm=HZN8irTUDDPu95k9SFatCcanUJBAy-MEjx9mt-PJb2g@mail.gmail.com> (raw)
In-Reply-To: <SN7PR11MB74653C0C276CD27DE0CCD886D74CA@SN7PR11MB7465.namprd11.prod.outlook.com> (Shynur Xie's message of "Sun, 4 Jun 2023 09:03:07 +0000")
Shynur Xie <one.last.kiss@outlook.com> writes:
>> From: Po Lu
>> Date: Sun, 04 Jun 2023 16:48:00 +0800
>> To: Shynur
>>
>> I believe you're experiencing intentional behavior: by default, text
>> is copied when the buffer which receives the drop is different from
>> its source.
>
> The destination buffer is the original buffer. I attached an MP4.
The video shows that text is copied also when the buffer which receives
the drop is the same as the source buffer.
Is that the intended behavior? It seems off, to me.
next prev parent reply other threads:[~2023-09-06 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 13:35 bug#63872: [PATCH] `mouse-drag-and-drop-region' sometimes couldn't cut Shynur Xie
2023-06-03 13:52 ` Shynur Xie
2023-06-04 0:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 8:38 ` Shynur Xie
2023-06-04 8:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <SN7PR11MB74653C0C276CD27DE0CCD886D74CA@SN7PR11MB7465.namprd11.prod.outlook.com>
2023-06-04 10:50 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 10:57 ` Stefan Kangas [this message]
2023-09-06 11:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 12:07 ` 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='CADwFkm=HZN8irTUDDPu95k9SFatCcanUJBAy-MEjx9mt-PJb2g@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=63872@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=one.last.kiss@outlook.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).