Re: mouse-yank-primary and bug #7699

[Eli Zaretskii <eliz@gnu.org>]

> Date: Wed, 22 Dec 2010 01:05:52 +0000
> From: David De La Harpe Golden <david@harpegolden.net>
> 
> > My question is: could switching the order do the wrong thing on X?
> 
> I expect so. See discussions under #6635, #6802.  x-get-selection-value 
> (or the x-selection-value-internal it calls) is doing the relevant dance 
> to get unicode.

Thanks (both to you and Jan) for the pointers and the feedback.

What is still unclear to me (but not entirely relevant to the issue at
hand in bug #7699) is why do we call x-get-selection at all, when
x-get-selection-value returns nil?  What situation does this second
call take care of?  (I'm asking because my conclusion both from
reading the X implementation and from your responses, and also from
discussions archived in bugs #6635 and #6802, is that x-get-selection
is roughly a limited variant of x-get-selection-value, in that it
supports less data types.  But I'm probably still missing something.)

> Anyway, mutating the new binding of mouse-2 until it acts like a creepy 
> zombie version of the old binding seems ...a relatively awkward path to 
> take.

The bug report I'm talking about was not about restoring Emacs 23
behavior of mouse-2.  It is about having mouse-2 in Emacs 24 paste the
w32 emulated "primary selection", at least when the selection was made
in the same Emacs session (which is the limit of what we can currently
do on Windows).  I believe that on X, Drew's recipe works as expected,
i.e. the mouse-selected text is pasted, not the text in the clipboard.
I'm trying to do the same on Windows, without any rebinding of keys.