unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jason Rumney'" <jasonr@gnu.org>, <bug-gnu-emacs@gnu.org>
Subject: bug#6689: 24.0.50; No primary selection
Date: Wed, 4 Aug 2010 23:51:16 -0700	[thread overview]
Message-ID: <1C9FFC3B583741A2B1CCBBE45F99F1DB@us.oracle.com> (raw)
In-Reply-To: <4C5A4ED0.4030805@gnu.org>

> The changes that were made have been discussed numerous times in 
> response to user complaints over many years.

Good to hear.  In which thread can I find a proposal summarizing the changes
being made?  Point me to the proposal and discussion of the proposed changes,
please.  I would love to see where we're headed.  I cannot tell the bugs from
the intentional changes.

Eli says that the intended changes are not for Windows anyway, which is
reassuring.  And he says they are obvious to people familiar with Posix
selection - and as a consequence of that there was _no_ proposal or discussion.
You apparently don't agree.  So where's the proposal?

> and now we have ONE user

There are several bug reports regarding recent selection changes, only two of
which I submitted (including this one).

> insisting that it be put back to the broken state it was in before

Seems that Yidong and Eli and... have also acknowledged that at least some of
the recent selection changes are bugs - at least on Windows, which is the only
platform I've spoken of from experience with the recent builds.

> I'm not sure I've seen you offer a reason 
> other than "it changed therefore it is now 'unusable'".

Perhaps you need to read again - and learn to quote fairly while you're at it.
I gave specific recipes, and others have agreed that what I described are bugs.
And some have been fixed.

Do you find it a _feature_ that you can no longer copy from one Emacs session
and yank to another (with the mouse)?  Do you find it a _feature_ that mouse
selection cannot be followed by `C-y' to yank the selected text (that has been
fixed, I believe - except cross-session).  Do you find it a _feature_ that mouse
selection followed by `M-w' raises an error "No primary selection" (that too has
been fixed, I believe).  And so on.  Were those changes "discussed numerous
times in response to user complaints over many years"?

I don't think so.  I think they are bugs.  Which is OK.  But I was not sure they
were not intentional changes until others confirmed that.  Why?  Because I know
that there are some intentional changes being made wrt selection, and I do not
know what they are (no proposal or summary of the changes to be made, AFAICT).
I am relieved to hear from Eli that they will not (ultimately) affect Windows,
but I did not know that at first.

What more do you need than such bug recipes in the way of _reasons_ to fix these
things?  There are clearly some "wrinkles to be ironed out".  And they are
getting ironed out, which means that we are progressively returning to the way
things were (on Windows).  Why do you suppose we would be returning to that
previous "broken state"?  Just because we have ONE user who insists on it?






  reply	other threads:[~2010-08-05  6:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 15:06 bug#6689: 24.0.50; No primary selection Drew Adams
2010-07-22 21:20 ` David De La Harpe Golden
2010-07-22 21:35   ` Drew Adams
2010-07-22 22:16     ` Chong Yidong
2010-07-22 22:34       ` Drew Adams
2010-07-22 23:49         ` Juanma Barranquero
2010-07-23 10:36         ` Eli Zaretskii
2010-07-23 14:57           ` Drew Adams
2010-07-23 15:33             ` Eli Zaretskii
2010-07-23 16:14               ` Drew Adams
2010-08-04 20:43                 ` Drew Adams
2010-08-04 23:22                   ` David De La Harpe Golden
2010-08-05  0:19                     ` Drew Adams
2010-08-05  0:29                       ` Chong Yidong
2010-08-05  0:39                         ` Drew Adams
2010-08-05  5:40                       ` Jason Rumney
2010-08-05  6:51                         ` Drew Adams [this message]
2010-08-12 20:37                           ` Drew Adams
2010-08-05  3:04                   ` Eli Zaretskii
2010-08-14 15:47             ` Eli Zaretskii
2010-07-23 10:39   ` Eli Zaretskii

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=1C9FFC3B583741A2B1CCBBE45F99F1DB@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=jasonr@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).