From: Richard Stallman <rms@gnu.org>
To: monnier@iro.umontreal.ca
Cc: emacs-devel@gnu.org
Subject: Re: function-key-map
Date: Thu, 11 Oct 2007 22:46:04 -0400 [thread overview]
Message-ID: <E1IgAXM-0004ZF-PD@fencepost.gnu.org> (raw)
In-Reply-To: <18189.42302.211705.594331@gargle.gargle.HOWL> (raman@users.sf.net)
Stefan> Yes, it's still very useful. See for example how
Stefan> term/xterm.el uses both. Or term/x-win.el.
Stefan> I.e. it's useful to give optional remapping
Stefan> corresponding to alternative key-names.
Is there a reason to use `function-key-map' for this,
rather than `key-translation-map'? Is it so that they won't
be translated if they have bindings?
In any case, the name `function-key-map' doesn't fit this kind of
usage. I gave it that name because its main purpose was to map escape
sequences into function keys, but that job is now done by
`input-decode-map'.
So perhaps we should rename the current `function-key-map' to
`default-key-translation-map', then rename the current
`input-decode-map' to `function-key-map'.
What do you think?
next prev parent reply other threads:[~2007-10-12 2:46 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 ` Richard Stallman [this message]
2007-10-12 15:19 ` function-key-map Stefan Monnier
2007-10-13 0:18 ` function-key-map Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1IgAXM-0004ZF-PD@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 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.