From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Devel <emacs-devel@gnu.org>, Jason Rumney <jasonr@gnu.org>
Subject: Re: ignore is bound to <lwindow> but <lwindow> is META
Date: Mon, 03 Apr 2006 16:29:02 -0400 [thread overview]
Message-ID: <jwvu09atnrw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <44317D0D.9000802@student.lu.se> (Lennart Borgman's message of "Mon, 03 Apr 2006 21:52:45 +0200")
> Oh, I see. But is not that quite confusing?
Yes, I wouldn't call it a feature. But more generally, figuring out the
reverse mapping from a command (or an event) to its possible sources
(e.g. which physical key (with its name), or mouse movement) is between
difficult and impossible.
> There might be many ways to generate an event (I actually do not know),
> but when I see "foo is bound to M-c, ..." I believe that when I hit M-c
> Emacs will call foo. I suspect most users will expect the same.
> Is not key-translation-map a simple case?
Partly. It's relatively easy to check whether M-c will be affected or not
by key-translation-map, but it can be very hard to determine if
key-translation-map can translate some other event into M-c.
> Can't this be checked in help?
It could. And it might get us one step closer. But there are still many
more steps, some of which outside of Emacs's control and/or knowledge, and
additional steps get added every once in a while, sometimes without even
being aware of it.
Even without key-translation-map, the window-manager might catch the M-c
before Emacs sees it, or it might be bound via special-event-map, or ...
Stefan
prev parent reply other threads:[~2006-04-03 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 16:59 ignore is bound to <lwindow> but <lwindow> is META Lennart Borgman
2006-04-03 18:05 ` Stefan Monnier
2006-04-03 18:08 ` Jason Rumney
2006-04-03 18:22 ` Lennart Borgman
2006-04-03 19:33 ` Stefan Monnier
2006-04-03 19:52 ` Lennart Borgman
2006-04-03 20:29 ` Stefan Monnier [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvu09atnrw.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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.