From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: function-key-map
Date: Fri, 12 Oct 2007 20:18:34 -0400 [thread overview]
Message-ID: <E1IgUiA-00086d-4Z@fencepost.gnu.org> (raw)
In-Reply-To: <jwvlka874zb.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 12 Oct 2007 11:19:25 -0400)
Renaming input-decode-map to function-key-map would be a bad idea because it
would introduce an incompatibility: the behavior of input-decode-map is
different, so while some uses of function-key-map are better moved to
input-decode-map, others (such as the ones mentioned at the beginning of
this message) need to stay on function-key-map.
Ok.
Actually the name
function-key-map would also be bad because it would fail to describe what
the map does (and instead describes what it was meant for).
That is not necessarily a bad thing, but this map is not solely for
producing function keys. So lt's stay with `input-decode-map'.
Renaming function-key-map to `default-key-translation-map' would also seem
like a bad idea:
- the name seems to imply that it's the global binding of "the
buffer-local key-translation-map".
- the name suggests the behavior of that map will be the same as the behavior
of `key-translation-map' although in reality it is different.
Those are valid arguments against the name `default-key-translation-map',
but not against renaming to a different name.
Right now, in the term/*.el files that I've changed to take advantage of
input-decode-map, I've used "foo-alternative-maps" for the keymaps that
hold bindings that need to be added to function-key-map, so maybe we could
rename function-key-map to alternative-input-names-map or
fallback-input-rename-map?
"Alternative" does not clearly describe the functionality, but
"fallback" does. (I used "default" for the same meaning.)
So how about `key-fallback-alias-map'?
next prev parent reply other threads:[~2007-10-13 0:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 13:00 function-key-map Richard Stallman
2007-10-10 14:31 ` function-key-map Stefan Monnier
2007-10-11 4:23 ` function-key-map T. V. Raman
2007-10-11 13:55 ` function-key-map Stefan Monnier
2007-10-12 1:17 ` function-key-map T. V. Raman
2007-10-12 2:46 ` function-key-map Richard Stallman
2007-10-12 15:19 ` function-key-map Stefan Monnier
2007-10-13 0:18 ` Richard Stallman [this message]
2007-10-13 3:46 ` function-key-map Stefan Monnier
2007-10-13 14:14 ` function-key-map Richard Stallman
2007-10-14 18:58 ` function-key-map Stefan Monnier
2007-10-15 16:03 ` function-key-map Richard Stallman
2007-10-16 20:31 ` function-key-map Stefan Monnier
2007-10-11 5:19 ` function-key-map Richard Stallman
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=E1IgUiA-00086d-4Z@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).