From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29478@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#29478: 26.0.90; `C-h k' followed by mouse clicks no longer shows down event
Date: Fri, 22 Dec 2017 22:05:49 +0000 [thread overview]
Message-ID: <20171222220549.GC8072@ACM> (raw)
In-Reply-To: <83tvwzubez.fsf@gnu.org>
Hello, Eli.
On Sat, Dec 09, 2017 at 18:13:40 +0200, Eli Zaretskii wrote:
> I think I found one more problem with Help functions on mouse clicks.
> Try this in "emacs -Q":
> C-h c S-mouse-1
> C-h k S-mouse-1
> In Emacs 25.2 these produce the description of mouse-appearance-menu,
> as expected, saying it's the binding of S-down-mouse-1. Emacs
> 26.0.90 does the same for "C-h c", but claims S-mouse-1 is undefined
> if you invoke "C-h k". The current emacs-26 branch claims S-mouse-1
> is undefined for both "C-h c" and "C-h k".
> I think this means that we have similar problems with any explicit
> bindings to S-down-mouse-N clicks.
> This is a regression that I think we must fix before releasing Emacs
> 26.1.
OK, I'm looking at this now. It's not as easy as I was hoping.
One phenomenon is puzzling me - it feels like a bug:
(i) emacs-26 -Q
(ii) M-: (read-key-sequence "prompt: ") <CR>
(iii) <shift>-mouse-1
What happens now is the key sequence is displayed, a S-down-mouse-1
event, but immediately overwritten in the message area by
<S-mouse-1> is undefined
. Why? I merely asked for the key sequence. I didn't ask for it to be
looked up in any key maps. What is doing the translation from a
shift-down-mouse event to a S-click event? What is looking up this
down-mouse event in a key map?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-12-22 22:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 23:21 bug#29478: 26.0.90; `C-h k' followed by mouse clicks no longer shows down event Drew Adams
2017-11-28 1:50 ` Noam Postavsky
2017-11-28 17:11 ` Eli Zaretskii
2017-11-28 22:10 ` Alan Mackenzie
2017-11-29 0:44 ` Noam Postavsky
2017-11-29 3:36 ` Eli Zaretskii
2017-11-29 4:33 ` Drew Adams
2017-12-01 8:31 ` Eli Zaretskii
2017-12-09 17:18 ` Alan Mackenzie
2017-12-23 14:28 ` bug#29478: [Patch 2]: " Alan Mackenzie
2017-12-23 14:48 ` Andreas Schwab
2017-12-24 8:43 ` Alan Mackenzie
[not found] ` <<20171128221036.GC14868@ACM>
[not found] ` <<bbcb1d00-a728-4b5e-b65f-bd2b168c4a51@default>
[not found] ` <<83o9ni3l3i.fsf@gnu.org>
2017-12-01 15:35 ` Drew Adams
2017-12-01 16:51 ` Eli Zaretskii
2017-12-09 16:13 ` Eli Zaretskii
2017-12-09 17:23 ` Alan Mackenzie
2017-12-22 22:05 ` Alan Mackenzie [this message]
2017-12-23 9:42 ` Eli Zaretskii
2017-12-23 11:17 ` bug#29478: [Patch] " Alan Mackenzie
2017-12-23 12:41 ` Eli Zaretskii
2017-12-23 16:33 ` Stefan Monnier
2017-12-23 21:04 ` Alan Mackenzie
2017-12-24 4:55 ` Stefan Monnier
2017-12-24 5:41 ` Eli Zaretskii
2017-12-24 6:52 ` Stefan Monnier
2017-12-24 11:48 ` Alan Mackenzie
2017-12-24 15:41 ` Stefan Monnier
2017-12-30 10:50 ` Eli Zaretskii
2018-01-03 3:56 ` Stefan Monnier
2018-01-06 17:40 ` Eli Zaretskii
2018-01-07 15:31 ` bug#29478: [SUSPECTED SPAM] " Stefan Monnier
2018-01-07 17:46 ` Eli Zaretskii
2018-01-07 18:03 ` Stefan Monnier
2018-01-26 22:00 ` bug#29478: " Stefan Monnier
2018-01-26 22:37 ` Stefan Monnier
2018-01-27 8:28 ` Eli Zaretskii
2018-01-28 16:02 ` Stefan Monnier
2018-01-28 17:18 ` Eli Zaretskii
2018-01-29 21:54 ` Stefan Monnier
2018-01-30 3:23 ` Eli Zaretskii
2018-01-30 14:18 ` Stefan Monnier
2018-01-30 15:40 ` Eli Zaretskii
2018-01-30 16:59 ` Stefan Monnier
2018-01-27 7:59 ` Eli Zaretskii
2017-12-30 10:51 ` Eli Zaretskii
2017-12-30 11:32 ` Alan Mackenzie
2017-12-30 12:49 ` Eli Zaretskii
2017-12-23 16:19 ` bug#29478: " Stefan Monnier
2020-08-26 13:43 ` bug#29478: 26.0.90; " Lars Ingebrigtsen
2020-08-26 17:12 ` Drew Adams
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=20171222220549.GC8072@ACM \
--to=acm@muc.de \
--cc=29478@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).