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: Tue, 03 Oct 2017 17:33:06 +0300 [thread overview]
Message-ID: <83r2uk1eu5.fsf@gnu.org> (raw)
In-Reply-To: <8760bwridy.fsf@gmail.com> (message from Alex on Mon, 02 Oct 2017 21:59:37 -0600)
> From: Alex <agrambot@gmail.com>
> Cc: 14793@debbugs.gnu.org, npostavs@users.sourceforge.net, regularclockwork@gmail.com
> Date: Mon, 02 Oct 2017 21:59:37 -0600
>
> > I just asked that question because my reading of the code is that this
> > is not supported. Maybe I'm misreading: keyboard.c:read_char is not
> > for the faint at heart.
>
> Yeah, I'm having trouble going through it. Is there a way to make it
> supported, though? For example, what about catching the error around
> read_char_x_menu_prompt (keyboard.c:L2683) and not exiting if an error
> was thrown?
That's hardly a clean solution. A clean solution would avoid calling
Fx_popup_menu when it detects the situation we are talking about.
> >> Also, "(emacs) Mouse Buttons" states that "You can put more than one
> >> mouse button in a key sequence, but it isn’t usual to do so.".
> >>
> >> How would one do this if a mouse click can't be a prefix key?
> >
> > By making a menu, I presume.
>
> Do you mean those mentioned in "(emacs) Menu Mouse Clicks"? Does
> clicking in those menus count as key sequences?
Yes, of course. You can see that with "C-h l", for example. Also,
every non-leaf menu item is a keymap.
next prev parent reply other threads:[~2017-10-03 14:33 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 [this message]
2017-10-05 3:58 ` Alex
2017-10-05 7:55 ` Eli Zaretskii
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=83r2uk1eu5.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).