From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12204@debbugs.gnu.org
Subject: bug#12204: 24.1.50; Binding mouse-movement interferes with "C-h c" for mouse clicks
Date: Mon, 12 Jun 2017 13:15:24 -0400 [thread overview]
Message-ID: <CAM-tV-8YpjhDHRpJwc2YoyXX8Q0fM1QNqhBx6DsQ85rwvb_mtQ@mail.gmail.com> (raw)
In-Reply-To: <83r2yp3zjr.fsf@gnu.org>
On Mon, Jun 12, 2017 at 1:07 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Noam Postavsky <npostavs@users.sourceforge.net>
>> Date: Mon, 12 Jun 2017 12:58:07 -0400
>> Cc: 12204@debbugs.gnu.org
>>
>> On Mon, Jun 12, 2017 at 10:10 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> >>
>> >> Perhaps describe-key could respect 'use-dialog-box' and popup a dialog
>> >> box when the "key" comes from the mouse?
>> >
>> > What would be shown in the dialog box?
>>
>> The usual message: "<mouse-movement> runs the command gud-tooltip-mouse-motion"
>
> That could look weird on systems that don't (yet) support dialog
> boxes, and use menus to emulate them. Like MS-Windows, for example,
> or text-mode terminals with a mouse.
>
> I was actually thinking seriously to not show the help message for
> mouse-movement bindings. Would that break something important?
It should only break discovery of what's bound to <mouse-movement> I
guess, and we could still leave "C-h k" for that so it shouldn't be
much of a problem.
next prev parent reply other threads:[~2017-06-12 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 19:07 bug#12204: 24.1.50; Binding mouse-movement interferes with "C-h c" for mouse clicks Eli Zaretskii
2017-06-12 0:18 ` npostavs
2017-06-12 14:10 ` Eli Zaretskii
2017-06-12 16:58 ` Noam Postavsky
2017-06-12 17:07 ` Eli Zaretskii
2017-06-12 17:15 ` Noam Postavsky [this message]
2017-06-12 17:20 ` Eli Zaretskii
2017-06-25 3:18 ` npostavs
2017-06-25 13:49 ` Eli Zaretskii
2017-07-01 14:10 ` npostavs
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-8YpjhDHRpJwc2YoyXX8Q0fM1QNqhBx6DsQ85rwvb_mtQ@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=12204@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.