From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 14793@debbugs.gnu.org, regularclockwork@gmail.com,
npostavs@users.sourceforge.net
Subject: bug#14793: 23.4; Cannot bind a function to a sequence of two mouse keys
Date: Thu, 05 Oct 2017 10:55:11 +0300 [thread overview]
Message-ID: <83fuayxc4g.fsf@gnu.org> (raw)
In-Reply-To: <87vajuutxq.fsf@gmail.com> (message from Alex on Wed, 04 Oct 2017 21:58:41 -0600)
> From: Alex <agrambot@gmail.com>
> Cc: 14793@debbugs.gnu.org, npostavs@users.sourceforge.net, regularclockwork@gmail.com
> Date: Wed, 04 Oct 2017 21:58:41 -0600
>
> There are a couple issues that I can see though, regarding double/triple
> clicks. First, evaluate the following:
>
> (define-prefix-command 'test)
> (global-set-key [mouse-3] #'test)
> (global-set-key [mouse-3 mouse-1] #'forward-word)
>
> 1. Triple clicking mouse-3 results in a popup menu that seems like it
> shouldn't appear, but this is also case when triple clicking
> C-mouse-3 even without my patch. I'm not sure what it's doing there.
>
> 2. Double clicking mouse-3 usually results in a mouse-3 double-mouse-3
> sequence, instead of double-mouse-3. You can tell by also evaluating:
>
> (global-set-key [mouse-3 double-mouse-3] #'forward-line)
> (global-set-key [double-mouse-3] #'goto-line)
>
> With the above key set, double clicking mouse-3 calls `forward-line',
> and oddly enough _triple_ clicking mouse-3 calls `goto-line'. Here's what
> `describe-key' has to say about triple clicking mouse-3:
>
> <double-mouse-3> (translated from <triple-down-mouse-3>
> <triple-mouse-3>) runs the command goto-line
>
> I have no idea why that translation exists.
>
> Do you have any ideas on how to solve these issues (especially getting
> double click to issue double-mouse-#)?
No ideas at the moment, but I think we should first decide whether we
want to allow mouse clicks as prefix keys. What are the practical
gains that justify messing with read_char on this behalf? We already
have the equivalent functionality via menus, right?
Not that I want to discourage you from digging into these issues ;-)
Thanks.
prev parent reply other threads:[~2017-10-05 7:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 17:14 bug#14793: 23.4; Cannot bind a function to a sequence of two mouse keys Stefano Lodi
2013-07-04 20:12 ` bug#14793: Further important info Stefano Lodi
[not found] ` <878twa94c5.fsf@users.sourceforge.net>
2017-10-01 3:05 ` bug#14793: 23.4; Cannot bind a function to a sequence of two mouse keys Alex
2017-10-01 16:02 ` Eli Zaretskii
2017-10-01 17:53 ` Alex
2017-10-01 18:26 ` Eli Zaretskii
2017-10-03 3:59 ` Alex
2017-10-03 14:33 ` Eli Zaretskii
2017-10-05 3:58 ` Alex
2017-10-05 7:55 ` Eli Zaretskii [this message]
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=83fuayxc4g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14793@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=regularclockwork@gmail.com \
/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).