unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: greenwaters <regularclockwork@gmail.com>
To: Help-gnu-emacs@gnu.org
Subject: Re: Binding mouse key sequences
Date: Thu, 4 Jul 2013 02:50:48 -0700 (PDT)	[thread overview]
Message-ID: <1372931448427-291164.post@n5.nabble.com> (raw)
In-Reply-To: <87fvvw1or9.fsf@web.de>

Thank you for answering Michael. 
I'll try to answer your questions adding some new facts.

1. Yes, it happens with emacs -Q.

2. After calling emacs -Q, C-h k mouse-8 gives

 <mouse-8> (translated from <down-mouse-8> <mouse-8>) at that spot is
undefined

Similar behaviour for C-h k mouse-9.
After binding with 

(global-set-key   [mouse-8 mouse-9] 'write-file)

C-h k mouse-8 gives

byte-code: Empty menu

3. However, after binding with

(global-set-key   [mouse-8] 'write-file)

C-h k mouse-8 gives the usual info 

<mouse-8> (translated from <down-mouse-8> <mouse-8>) at that spot runs
the command write-file, which is an interactive compiled Lisp
function.

It is bound to <mouse-8>, C-x C-w, <menu-bar> <file> <write-file>.

etc.

and mouse-8 pops up the file selector window.

4. Now, setting 

 (global-set-key [mouse-8 mouse-9] 'write-file) 

and executing

(progn
    (push 'mouse-9 unread-command-events)
    (push 'mouse-8 unread-command-events))

does indeed call write-file.

5. I used xev to catch mouse key press events in Xorg: both mouse-8 and
mouse-9 are recognized. This does not tell me much, however, because the
test used xev's own window. When I tell xev to monitor any other window,
e.g., emacs, mouse clicks are not catched by xev. 

6. Setting the debug variable to true gives simply 

Debugger entered--Lisp error: (error "Empty menu")

I replicated the tests above using mouse-3 instead of mouse-8 and mouse-2
instead of mouse-9. Therefore I doubt there's any relation with high
numbered mouse buttons in Xorg.

This is all I was able to find out, with one addition: double-mouse-8 or
drag-mouse-8 always pops up a menu with just two entries, "tool bar" and
"Menu bar", both giving access to submenus. The former has entries for all
the buttons in the emacs tool bar, but all entries seem disabled. The latter
equals the Lisp-Interaction menu (I am performing tests inside the scratch
buffer). Same using mouse-3 and mouse-2, or using S-mouse-3 and mouse-2;
therefore it looks definitely as an effect of using global-set-key, and not
some predefined undocumented behavior. Moreover, globally unsetting
double-mouse-8 leaves that menu still functional.

BTW I am using 

GNU Emacs 23.4.1 (i486-pc-linux-gnu, GTK+ Version 2.24.10)
GNU Emacs 23.4.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.10)

on Debian Wheezy.

Any further hint is welcomed.




--
View this message in context: http://emacs.1067599.n5.nabble.com/Binding-mouse-key-sequences-tp291017p291164.html
Sent from the Emacs - Help mailing list archive at Nabble.com.



  reply	other threads:[~2013-07-04  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 22:48 Binding mouse key sequences greenwaters
2013-07-03  0:16 ` Michael Heerdegen
2013-07-04  9:50   ` greenwaters [this message]
2013-07-04 14:40     ` Michael Heerdegen
2013-07-04 16:36       ` greenwaters

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=1372931448427-291164.post@n5.nabble.com \
    --to=regularclockwork@gmail.com \
    --cc=Help-gnu-emacs@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.
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).