From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Smith <rsmithnews@gmail.com>
Cc: 17211@debbugs.gnu.org
Subject: bug#17211: Empty items show up in kill-ring if mouse-drag-copy-region is used
Date: Wed, 11 May 2022 15:31:29 +0200 [thread overview]
Message-ID: <87ee108aby.fsf@gnus.org> (raw)
In-Reply-To: <CACE1RH1kLpiRiv==N3jesD3NFCeS+d6SeXqy_mKxp43wjg2zRA@mail.gmail.com> (Richard Smith's message of "Sun, 6 Apr 2014 14:53:21 -0700")
Richard Smith <rsmithnews@gmail.com> writes:
> 7. Now, set up the "modified behavior" by executing this form:
>
> (progn
> (setq select-active-regions nil)
> (setq mouse-drag-copy-region t)
> (global-set-key [mouse-2] 'mouse-yank-at-click))
>
> 8. Repeat steps 3 thru 5.
>
> 9. Observe that nothing is pasted.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I can reproduce the behaviour you're seeing in Emacs 29, but I'm not
sure what else Emacs could do here. With `mouse-drag-copy-region' set,
and in 4) you drag the mouse, so it copies that new region (even if that
region is so short that you end up with "").
Hm... well, I guess we could change mouse-drag-copy-region so that if
the region is very short (i.e., less than a character), then we don't
put that onto the kill ring?
Does anybody here object to making such a change? I guess it's possible
that somebody is using a sub-character drag to set the mark, but it does
seem unlikely.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-11 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 21:53 bug#17211: Empty items show up in kill-ring if mouse-drag-copy-region is used Richard Smith
2022-05-11 13:31 ` Lars Ingebrigtsen [this message]
2022-05-11 14:35 ` Drew Adams
2022-06-09 13:58 ` Lars Ingebrigtsen
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=87ee108aby.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=17211@debbugs.gnu.org \
--cc=rsmithnews@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).