bug#6694: 24.0.50; mouse-yank-primary tries to yank a *buffer*

bug#6694: 24.0.50; mouse-yank-primary tries to yank a *buffer*

[Drew Adams]

I click mouse-1 at the left of some text and then mouse-3 at the right
of it, to select it (a Lisp symbol).  Then I try to yank it using
`mouse-2':
 
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p #<buffer
throw-x-at-pt.el>)
  mouse-yank-primary((mouse-2 (#<window 8 on throw-x-at-pt.el> 4906 (392 . 488)
12477031 nil 4906 (49 . 33) nil (224 . 9) (8 . 14))))
  call-interactively(mouse-yank-primary nil nil)
 
Yanking it with C-y works OK.  So the problem is not with what was
copied but with `mouse-yank-primary'.
 
This is silly.  Please restore the normal copy/paste behavior for the
mouse.  It seems completely broken now.

In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
 of 2010-07-19 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4) --no-opt --cflags -Ic:/xpm/include'
 

bug#6694: 24.0.50; mouse-yank-primary tries to yank a *buffer*

[Drew Adams]

Correction: Clicking mouse-1, then mouse-3 apparently does *not* copy the
selection to the kill ring.  When I said that C-y worked, I must have used M-w
first.

Without M-w, C-y doesn't work either (after selecting using mouse-1, 3).

The mouse should work normally for selection and wrt the kill-ring.
This is Emacs.

bug#6694: 24.0.50; mouse-yank-primary tries to yank a *buffer*

[David De La Harpe Golden]

On 21/07/10 18:49, Drew Adams wrote:
> I click mouse-1 at the left of some text and then mouse-3 at the right
> of it, to select it (a Lisp symbol).  Then I try to yank it using
> `mouse-2':
>
> Debugger entered--Lisp error: (wrong-type-argument char-or-string-p #<buffer
> throw-x-at-pt.el>)

Ah, this would be a genuine bug, then.

What's happening here is that w32's internal emulation of a primary is 
incomplete - relatively recently, it became valid on canonical x11 emacs 
to  set selection to a buffer (or a cons of markers), with the meaning 
the selection is (lazily) the string between the point and mark of the 
buffer (or the markers).

w32's fake selection handling needs update to include this possibility.

(It needs this update regardless of changes to the defaults, the 
defaults have just successfully thrown a spotlight on the breakage).

bug#6694: 24.0.50; mouse-yank-primary tries to yank a *buffer*

[Chong Yidong]

> I click mouse-1 at the left of some text and then mouse-3 at the right
> of it, to select it (a Lisp symbol).  Then I try to yank it using
> `mouse-2':
>
> Debugger entered--Lisp error: (wrong-type-argument char-or-string-p #<buffer
> throw-x-at-pt.el>)

This should be fixed now; Emacs no longer uses this mechanism for
setting the primary.