From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 7077@debbugs.gnu.org
Subject: bug#7077: 24.0.50; mouse-drag-copy-region - name should say copy as kill
Date: Sun, 03 Jul 2011 16:02:34 +0200 [thread overview]
Message-ID: <m339inlax1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <7E487051D23B4BCC9AC15FFF312E8788@us.oracle.com> (Drew Adams's message of "Sat, 2 Jul 2011 08:46:24 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
>> I think that sounds reasonable, but, on the other hand, is it really
>> necessary for all these functions to mention "kill" in the function
>> name? It seems intuitive (to me) that `mouse-drag-copy-region' puts
>> stuff in the kill ring -- what else would it do?
>
> 1. "Copy" can mean a couple different things. One misunderstanding
> might be to copy the region to another location in a buffer - a la
> copy + paste.
>
> 2. It's helpful for Emacs to be consistent and put important Emacs
> terms into command names that involve them.
That's true, but I'm not sure that this consistency is worth renaming
user-visible customisation variables just to be that consistent.
I was confused -- I thought `mouse-drag-copy-region' was a function, but
it's a variable, which makes renaming even more of a problem, in my
opinion.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-03 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 20:39 bug#7077: 24.0.50; mouse-drag-copy-region - name should say copy as kill Drew Adams
2011-07-02 14:22 ` Lars Magne Ingebrigtsen
2011-07-02 15:46 ` Drew Adams
2011-07-03 14:02 ` Lars Magne Ingebrigtsen [this message]
2011-07-03 14:23 ` Drew Adams
2011-07-03 18:38 ` Chong Yidong
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=m339inlax1.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=7077@debbugs.gnu.org \
--cc=drew.adams@oracle.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).