Re: [Emacs-diffs] master 9a83ecb: Refer to local-function-key-map in various manuals

[Lars Ingebrigtsen <larsi@gnus.org>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Actually, they should mostly use `input-decode-map` instead nowadays (the
> difference is that `input-decode-map`'s remapping is applied
> unconditionally, where `(local-)function-key-map`'s remapping is only
> applied when there's no normal keybinding).

I've now changed the two instances to refer to input-decode-map (only).

>>  @smallexample
>>  ;; @r{Make the @key{ENTER} key from the numeric keypad act as @kbd{C-j}.}
>> -(define-key function-key-map [kp-enter] [?\C-j])
>> +(define-key local-function-key-map [kp-enter] [?\C-j])
>
> This remapping should probably be applied to any terminal that has
> a kp-enter key, so I think the change is for the worse.

Makes sense...  but should we then change the bit in the manual that
says:

@code{local-function-key-map} inherits from @code{function-key-map},
but the latter should not be used directly.

Perhaps we should change that to something that says more explicitly
what the effect of using function-key-map is?  Something like "which
should only be used if you want the changes in all terminals"?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no