GNU bug report logs - #20398
25.0.50; Clicking `window-divider-last-pixel' in help for `window-divider'

Previous Next

Full log

Message #26 received at 20398 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: rgm <at> gnu.org, 20398 <at> debbugs.gnu.org
Subject: Re: bug#20398: 25.0.50;
 Clicking `window-divider-last-pixel' in help for `window-divider'
Date: Thu, 23 Apr 2015 13:37:16 +0300

> Date: Thu, 23 Apr 2015 09:50:33 +0200
> From: martin rudalics <rudalics <at> gmx.at>
> CC: 20398 <at> debbugs.gnu.org
> 
> I'm troubled by
> 
> 
> Debugger entered--Lisp error: (error "No selection is available")
>    signal(error ("No selection is available"))
>    error("No selection is available")
>    gui-get-primary-selection()
>    mouse-yank-primary((mouse-2 (#<window 3 on *Customize Face: window-divider*> 615 (355 . 257) 4390875 nil 615 (42 . 14) nil (3 . 7) (8 . 16))))
>    funcall-interactively(mouse-yank-primary (mouse-2 (#<window 3 on *Customize Face: window-divider*> 615 (355 . 257) 4390875 nil 615 (42 . 14) nil (3 . 7) (8 . 16))))
>    call-interactively(mouse-yank-primary nil nil)
>    command-execute(mouse-yank-primary)
> 
> 
> with <mouse-1> on any such link in a customization buffer.  Can anyone
> see this?

I see this.  Everyone should, AFAICS.

> Does anyone have an idea where this mouse-2 yanking attempt comes
> from?

It comes from the command loop.  I think mouse-1 remapping, as
implied by the return value of mouse-on-link-p, has something to do
with that.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.