unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Miles Bader'" <miles@gnu.org>,
	"'Chong Yidong'" <cyd@stupidchicken.com>
Cc: 'David De La Harpe Golden' <david@harpegolden.net>, emacs-devel@gnu.org
Subject: RE: Selection changes
Date: Thu, 22 Jul 2010 14:21:25 -0700	[thread overview]
Message-ID: <04B92DEADC9D46F38CB42B91679795DE@us.oracle.com> (raw)
In-Reply-To: <878w5a23ax.fsf@catnip.gol.com>

> Chong Yidong <cyd@stupidchicken.com> writes:
> > But I think select-active-regions needs further 
> > improvement.  Perhaps its default behavior should be as
> > follows: for an active region created using
> > shift-selection or mouse dragging, Emacs supplies the 
> > region text to primary.  When such a region is
> > deactivated, Emacs disowns primary (as some other apps
> > do, tho not Firefox).  For an active region created
> > simply with C-SPC, no special x-selection handling should 
> > be performed.
> 
> I don't like things that make selections magic depending on how they
> were selected; it just makes the interface more confusing and
> discourages people from learning new commands.
> 
> A selection should be a selection, to the greatest extent possible
> (there are some exceptions, like shift-selections auto-deselecting,
> but that's much less confusing because it's an immediate and visually
> obvious effect, and fits people's shift-select muscle-memory).

I agree with Miles about that.

I'll go further, on a different angle.  I disagree with a change to the default
behavior of selection/kill/copy/yank (with the mouse or keyboard).  Period.  

The latest build I have of Emacs is completely broken wrt yanking with mouse-2 -
see bugs 6689, 6694, 6701,....  I have not paid attention to this thread, but I
cannot ignore a blown-away mouse.

I don't know what problem you all think you're trying to fix, but AFAICT nothing
needs fixing wrt select/kill/copy/yank, whether via keys or mouse.  It ain't
broke, so please stop trying to fix it.  I use the kill ring, primary selection,
and secondary selection all the time, and they all work just fine, thank you
very much - both within Emacs and between it and other apps.  Or they did until
recently.

There are so many real bugs that need fixing - many with solutions already
provided.  Why not start there, if you have the time and energy to fiddle?

If you want to provide an optional (opt-in), _alternative_ behavior for
select/kill/copy/yank (mouse or keyboard or both), then fine - go for it.  Bring
that up here as a _proposal_, to be discussed.  No problem.  Normal.

But no such a change should be made to the _default_ behavior.  I cannot
understand how such changes are made willy nilly, without any real discussion.
That's not the way Emacs development should proceed.

When someone does propose a change here, it can be nigh unto impossible to get
any agreement and the final OK for it.  I understand that very well, believe me.
But that does not mean that having commit access is a license to make whatever
changes you like.  And that applies to everyone, or it should.

It's not kosher to avoid full proposal & discussion and just implement whatever
you think is right.  That doesn't respect the community, and it's not good
development practice that leads to a good product.

Just one opinion, of course.





  parent reply	other threads:[~2010-07-22 21:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 18:08 Selection changes Chong Yidong
2010-07-14 18:39 ` Jeff Clough
2010-07-14 18:53   ` Chong Yidong
2010-07-14 19:02     ` Jeff Clough
2010-07-14 19:25 ` Yann Hodique
2010-07-14 20:28   ` Chong Yidong
2010-07-14 23:51 ` David De La Harpe Golden
2010-07-16  1:31 ` Richard Stallman
2010-07-16  2:49   ` Miles Bader
2010-07-17  0:44 ` David De La Harpe Golden
2010-07-17  1:02   ` Miles Bader
2010-07-17  2:28     ` David De La Harpe Golden
2010-07-17  2:56       ` Chong Yidong
2010-07-17  3:30         ` Miles Bader
2010-07-17  3:49           ` Chong Yidong
2010-07-22 21:21           ` Drew Adams [this message]
2010-07-22 22:05             ` Chong Yidong
2010-07-23 10:32               ` Eli Zaretskii
2010-07-24 18:44                 ` David De La Harpe Golden
2010-07-24 20:28                   ` Eli Zaretskii
2010-07-24 21:48                     ` David De La Harpe Golden
2010-07-25 16:32                   ` David De La Harpe Golden
2010-07-17  3:50         ` David De La Harpe Golden
2010-07-17  3:55           ` Chong Yidong
2010-07-17  4:13             ` Chong Yidong
2010-07-17 16:55               ` David De La Harpe Golden
2010-07-18 16:24               ` David De La Harpe Golden
2010-07-17 10:50         ` Wojciech Meyer
2010-07-17 11:01           ` Miles Bader
  -- strict thread matches above, loose matches on Subject: below --
2010-07-16  1:00 Angelo Graziosi
2010-07-16  9:33 ` David De La Harpe Golden
2010-07-17 23:49   ` Angelo Graziosi
2010-07-18 19:28     ` David De La Harpe Golden
2010-07-18 22:39       ` Angelo Graziosi
2010-07-16 12:14 ` Angelo Graziosi
2011-05-27 16:25 Chong Yidong
2011-05-28  4:13 ` David De La Harpe Golden
2011-05-31  0:59   ` Taylor Venable
2011-05-28 11:16 ` Andreas Röhler

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=04B92DEADC9D46F38CB42B91679795DE@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=cyd@stupidchicken.com \
    --cc=david@harpegolden.net \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).