From: Chong Yidong <cyd@stupidchicken.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 6956@debbugs.gnu.org
Subject: bug#6956: 24.0.50; pasting mouse selection in other session pastes only first word
Date: Sat, 04 Sep 2010 15:09:03 -0400 [thread overview]
Message-ID: <87hbi58gxc.fsf@stupidchicken.com> (raw)
In-Reply-To: <8339tpix6o.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Sep 2010 14:07:43 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Just curious, what about the case when you start with shift-select on
>> a few characters and then extend with mouse-3, is that a mouse drag
>> to be copied when mouse-drag-copy-region is t? Or double click word,
>> shift select to extend, mouse-3 to extend and then shift select to
>> extend, what goes into kill ring then? The "mouse" in
>> mouse-drag-copy-region makes these things difficult to figure out.
>
> I agree that this is confusing. So maybe we should decide that a
> "drag", for the purpose of mouse-drag-copy-region, does not include
> extending the selection with whatever means. Then, to pacify users
> who want Emacs 23 behavior, we will need either (a) introduce a new
> option, nil by default, which, when set non-nil, will copy selected
> text to the kill ring, or (b) decide that this is a Windows-only
> issue, and resolve it with a Windows-specific option with the same
> effect as in (a) above.
I'd rather not introduce another variable here. I don't object to
allowing mouse-save-then-kill obey mouse-drag-copy-region (the emphasis
being on the "mouse" rather than the "drag"), provided the doc of
mouse-drag-copy-region is updated accordingly.
Any user who insists on changing mouse-drag-copy-region back to t can
deal with the inconsistency.
next prev parent reply other threads:[~2010-09-04 19:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 16:48 bug#6956: 24.0.50; pasting mouse selection in other session pastes only first word Drew Adams
2010-08-31 17:26 ` Eli Zaretskii
2010-08-31 18:13 ` Chong Yidong
2010-09-01 14:38 ` Eli Zaretskii
2010-09-04 7:18 ` Eli Zaretskii
2010-09-04 8:35 ` Jan Djärv
2010-09-04 11:07 ` Eli Zaretskii
2010-09-04 15:06 ` Drew Adams
2010-09-04 15:44 ` Eli Zaretskii
2010-09-04 15:15 ` Jan Djärv
2010-09-04 19:09 ` Chong Yidong [this message]
2010-09-04 20:35 ` David De La Harpe Golden
2010-09-04 21:38 ` David De La Harpe Golden
2010-09-05 1:53 ` Chong Yidong
2010-09-05 5:33 ` David De La Harpe Golden
2010-09-05 14:36 ` David De La Harpe Golden
2010-09-05 3:09 ` Eli Zaretskii
2010-09-05 4:48 ` David De La Harpe Golden
2010-09-05 5:06 ` Eli Zaretskii
2010-09-04 17:06 ` David De La Harpe Golden
2010-08-31 18:16 ` Drew Adams
2010-09-16 20:02 ` Eli Zaretskii
2010-09-16 23:51 ` Drew Adams
2010-09-17 8:01 ` Eli Zaretskii
[not found] ` <3BE2421F73AD4292AE8375CA3328663D@us.oracle.com>
2010-09-17 16:14 ` Eli Zaretskii
2010-09-17 16:20 ` Drew Adams
2010-09-17 17:03 ` Eli Zaretskii
2010-09-20 18:47 ` Drew Adams
2010-09-20 19:18 ` Eli Zaretskii
2010-09-20 20:19 ` Drew Adams
2010-09-20 20:43 ` Drew Adams
2010-09-20 20:52 ` Eli Zaretskii
2010-09-20 21:41 ` Drew Adams
2010-09-20 21:53 ` Eli Zaretskii
2010-09-20 22:24 ` Drew Adams
2010-09-21 4:08 ` Eli Zaretskii
2010-09-21 14:20 ` Drew Adams
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=87hbi58gxc.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=6956@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).