From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 27490@debbugs.gnu.org
Subject: bug#27490: 24.5; Elisp manual explanation of `function-key-map' and its inheritors
Date: Sun, 21 Jul 2019 19:39:49 +0300 [thread overview]
Message-ID: <83sgqzqr3e.fsf@gnu.org> (raw)
In-Reply-To: <87v9vv4d2e.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Sun, 21 Jul 2019 17:33:45 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 21 Jul 2019 17:33:45 +0200
> Cc: 27490@debbugs.gnu.org
>
> This text:
>
> ------
>
> @code{local-function-key-map} inherits from @code{function-key-map},
> but the latter should not be used directly.
>
> ------
>
> was added by this commit:
>
> ------
>
> commit 6b9e769476955b928b0248fef5aaa0e40754e257
> Author: Eli Zaretskii <eliz@gnu.org>
> Date: Sat Jan 17 19:14:52 2009 +0000
>
> (Translation Keymaps): Rename function-key-map to local-function-key-map.
>
> ------
>
>
> So I'm assuming that there was a plan to phase out using
> function-key-map or something? Perhaps Eli can clarify.
I don't remember any details, and I found no discussions of this
around that date. However, you will find a bunch of commits around
that one which all renamed function-key-map to
local-function-key-map. So yes, it appears like we wanted people to
use the latter.
> But there's a bunch of examples in the manual that does use the map, so
> either these should be adjusted, or the documentation clarified:
I think the examples which use function-key-map should be modified,
yes.
> The only way to affect the behavior of keys within Emacs is through
> @code{xmodmap} (outside Emacs) or @code{define-key} (inside Emacs). The
> @code{define-key} command should be used in conjunction with the
> @code{function-key-map} map. For instance,
>
> @lisp
> (define-key function-key-map [M-@key{TAB}] [?\M-\t])
> @end lisp
Where did you find this? I must be blind, because I don't see this
passage in the manual.
next prev parent reply other threads:[~2019-07-21 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 20:33 bug#27490: 24.5; Elisp manual explanation of `function-key-map' and its inheritors Drew Adams
2019-07-21 15:33 ` Lars Ingebrigtsen
2019-07-21 16:39 ` Eli Zaretskii [this message]
2019-07-21 17:31 ` Lars Ingebrigtsen
2019-07-21 17:54 ` Eli Zaretskii
2019-07-21 18:16 ` Lars Ingebrigtsen
2019-07-23 14:58 ` Eli Zaretskii
2019-07-23 17:16 ` Lars Ingebrigtsen
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=83sgqzqr3e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27490@debbugs.gnu.org \
--cc=larsi@gnus.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.