From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29349@debbugs.gnu.org
Subject: bug#29349: [Patch] Bug 29349: read_key_sequence is only partially recursive. This is a bug.
Date: Mon, 20 Nov 2017 17:27:26 +0000 [thread overview]
Message-ID: <20171120172726.GA3917@ACM> (raw)
In-Reply-To: <83ine5ei9j.fsf@gnu.org>
Hello, Eli.
On Mon, Nov 20, 2017 at 05:33:28 +0200, Eli Zaretskii wrote:
> > Date: Sun, 19 Nov 2017 20:41:21 +0000
> > Cc: 29349@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>
[ .... ]
> > > .... and (b) why do we need the followup patch -- with the mouse-1
> > > events injected into the sequence the "translation" looks correct and
> > > even educational.
> > I don't think it looks correct. The C-down-mouse-3 which exists as an
> > essential part of the key sequence has been overwritten in the
> > "translation".
> That's not what I see here, with your patch applied in keyboard.c, I
> see this:
> <C-down-mouse-3> <indent-pp-sexp> (translated from <C-down-mouse-3>
> <mouse-1> <indent-pp-sexp>) at that spot runs the command
> indent-pp-sexp (found in global-map), which is an interactive compiled
> Lisp function in `lisp-mode.el'.
> So C-down-mouse-3 is still there, we just have each click in the menus
> injected into the sequence. What did you see after applying that
> patch.
Apologies. I wasn't paying enough attention to your post, and I was a
little confused.
> > The other thing is that if mouse-movements get into the raw event buffer
> > (which I've seen, but for some reason amn't seeing any more) the
> > "translated from" could become objectionably long.
> I don't see that as a problem.
OK.
> > I think the "translated from" bit is intended to document a sequence the
> > user is aware of (such as a double click) being translated into a
> > different sequence she's aware of (such as a single click).
> And that's exactly what happens in this case.
> > The mouse-1, I believe, is more part of the user's subconsciousness
> > rather than awareness.
> But those mouse-1 clicks are real.
OK, again. I think I would still prefer to suppress that "translated
from" message, but it's not a strong preference, and not a terribly
important point.
So, I'll get on and commit my patch to keyboard.c (to master), but leave
help.el alone. If those "translated from"s ever do get to be
objectionable, as measured by user response, we can always do something
about them later.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-11-20 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 9:38 bug#29349: read_key_sequence is only partially recursive. This is a bug Alan Mackenzie
2017-11-19 12:34 ` Alan Mackenzie
2017-11-19 15:59 ` bug#29349: [Patch] Bug 29349: " Alan Mackenzie
2017-11-19 17:01 ` Eli Zaretskii
2017-11-19 17:45 ` Alan Mackenzie
2017-11-19 18:02 ` Eli Zaretskii
2017-11-19 20:41 ` Alan Mackenzie
2017-11-20 3:33 ` Eli Zaretskii
2017-11-20 17:27 ` Alan Mackenzie [this message]
2017-11-20 18:24 ` Eli Zaretskii
2017-11-20 18:12 ` Alan Mackenzie
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=20171120172726.GA3917@ACM \
--to=acm@muc.de \
--cc=29349@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 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).