Re: Functionality of overriding-local-map

[Juri Linkov]

>>  if (!NILP (olp)
>>      /* The doc said that overriding-terminal-local-map should
>>         override overriding-local-map.  The code used them both,
>>         but it seems clearer to use just one.  rms, jan 2005.  */
>>      && NILP (KVAR (current_kboard, Voverriding_terminal_local_map))
>>      && !NILP (Voverriding_local_map))
>>    keymaps = Fcons (Voverriding_local_map, keymaps);
>>
>> It seems the doc isn't clear cut and there's not much more info to
>> accompany this commit d64cdc59724b7caca47913d5beb2b4a54f7b7c91.
>> I you want to change this behavior (or fix/improve the doc)
>> I recommend you `M-x report-emacs-bug`.
>
> I encountered this while using o-l-m as a buffer local map that
> overrides other buffer local maps, as it is intended.  o-t-l-m
> does not do this; the latter (current) behavior results in a
> loss of functionality.
>
> In my case, it prevented the use of universal-argument with commands
> in overriding-local-map.  As universal-argument uses set-transient-map,
> if next command isn't bound in universal-argument-map, it is looked up
> in next active keymap (current-global-map).  IMO, what should happen is
> that the next active keymap be overriding-local-map, as per
> "(elisp) Searching Keymaps."

This bites us in other places too.  Please see a possible solution in
https://lists.gnu.org/archive/html/emacs-devel/2021-05/msg00490.html