* bug#7077: 24.0.50; mouse-drag-copy-region - name should say copy as kill
@ 2010-09-20 20:39 Drew Adams
2011-07-02 14:22 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 6+ messages in thread
From: Drew Adams @ 2010-09-20 20:39 UTC (permalink / raw)
To: 7077
emacs -Q
The name does not say anything about copying to the kill ring. The name
should, like `kill-ring-save' and `copy-region-as-kill', say that this
copies to the kill ring.
Suggestion: `mouse-drag-copy-region-as-kill' or
`mouse-drag-kill-ring-save'.
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2010-09-20 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4) --no-opt --cflags
-Ic:/imagesupport/include'
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7077: 24.0.50; mouse-drag-copy-region - name should say copy as kill
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
0 siblings, 1 reply; 6+ messages in thread
From: Lars Magne Ingebrigtsen @ 2011-07-02 14:22 UTC (permalink / raw)
To: Drew Adams; +Cc: 7077
"Drew Adams" <drew.adams@oracle.com> writes:
> The name does not say anything about copying to the kill ring. The name
> should, like `kill-ring-save' and `copy-region-as-kill', say that this
> copies to the kill ring.
>
> Suggestion: `mouse-drag-copy-region-as-kill' or
> `mouse-drag-kill-ring-save'.
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?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7077: 24.0.50; mouse-drag-copy-region - name should say copy as kill
2011-07-02 14:22 ` Lars Magne Ingebrigtsen
@ 2011-07-02 15:46 ` Drew Adams
2011-07-03 14:02 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 6+ messages in thread
From: Drew Adams @ 2011-07-02 15:46 UTC (permalink / raw)
To: 'Lars Magne Ingebrigtsen'; +Cc: 7077
> > The name does not say anything about copying to the kill
> > ring. The name should, like `kill-ring-save' and
> > `copy-region-as-kill', say that this copies to the kill ring.
> >
> > Suggestion: `mouse-drag-copy-region-as-kill' or
> > `mouse-drag-kill-ring-save'.
>
> 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.
In particular, this makes it easy to find them using things like `apropos'.
This principle is at least as old as the Unix `apropos' command and similar. We
generally try to have Emacs commands that deal with buffer use `buffer' in the
name; those that deal with files use `file'; with yanking use `yank', etc.
It is not so obvious, especially to a newbie, that `mouse-drag-copy-region'
copies to the `kill-ring'. Especially now that there are multiple copy-target
thingies such as the clipboard, paste buffer, interprogram XYZ, etc. (I don't
know the correct names).
In the beginning Emacs had only the `kill-ring' for copying and pasting, but
even in that context it would be helpful for a command such as this to have a
name similar to `kill-ring-save' and `copy-region-as-kill', suggesting that it
copies to the kill ring.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7077: 24.0.50; mouse-drag-copy-region - name should say copy as kill
2011-07-02 15:46 ` Drew Adams
@ 2011-07-03 14:02 ` Lars Magne Ingebrigtsen
2011-07-03 14:23 ` Drew Adams
0 siblings, 1 reply; 6+ messages in thread
From: Lars Magne Ingebrigtsen @ 2011-07-03 14:02 UTC (permalink / raw)
To: Drew Adams; +Cc: 7077
"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/
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7077: 24.0.50; mouse-drag-copy-region - name should say copy as kill
2011-07-03 14:02 ` Lars Magne Ingebrigtsen
@ 2011-07-03 14:23 ` Drew Adams
2011-07-03 18:38 ` Chong Yidong
0 siblings, 1 reply; 6+ messages in thread
From: Drew Adams @ 2011-07-03 14:23 UTC (permalink / raw)
To: 'Lars Magne Ingebrigtsen'; +Cc: 7077
> 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.
Option names are important, including for finding the options in the first
place. We have a mechanism for renaming: create an alias and declare the old
name deprecated/obsolete. Nothing new here.
The old name will anyway live on for a while (past experience shows that it will
be quite a while). But even just the existence of the alias (a better name)
will mean that users will more easily find and recognize this option for what it
is. That's regardless of the deprecation; the alias is the improvement.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7077: 24.0.50; mouse-drag-copy-region - name should say copy as kill
2011-07-03 14:23 ` Drew Adams
@ 2011-07-03 18:38 ` Chong Yidong
0 siblings, 0 replies; 6+ messages in thread
From: Chong Yidong @ 2011-07-03 18:38 UTC (permalink / raw)
To: Drew Adams; +Cc: 7077, 'Lars Magne Ingebrigtsen'
"Drew Adams" <drew.adams@oracle.com> writes:
> Option names are important, including for finding the options in the
> first place. We have a mechanism for renaming: create an alias and
> declare the old name deprecated/obsolete. Nothing new here.
The improvement is too marginal to justify a rename + obsolete
declaration.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-07-03 18:38 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2011-07-03 14:23 ` Drew Adams
2011-07-03 18:38 ` Chong Yidong
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).