summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp
diff options
context:
space:
mode:
authorJonas Bernoulli <jonas@bernoul.li>2020-04-20 23:33:44 +0200
committerJonas Bernoulli <jonas@bernoul.li>2020-07-15 18:06:04 +0200
commit8c60347780937f87f8b5ff78e3e9372821cad89a (patch)
tree676867c75292b6cb1a8e65536760028efd68ef34 /lisp/emacs-lisp
parent9f82622d33b7e7558d1ba30781b209b599b24b52 (diff)
downloademacs-8c60347780937f87f8b5ff78e3e9372821cad89a.tar.gz
emacs-8c60347780937f87f8b5ff78e3e9372821cad89a.tar.bz2
emacs-8c60347780937f87f8b5ff78e3e9372821cad89a.zip
epa-key-list-mode-map: Use widget-keymap as parent keymap
Normally when one keymap is to be treated as the parent of another, then that relationship is setup once at the time when the child is being defined, i.e. at birth. For some reason, this was not done here; instead `widget-keymap' is set as `epa-key-list-mode-map' parent every time the former is setup to be used as the local map. This appears to be a mistake. A few other keymaps use `widget-keymap' as their parent and in those cases the relationship is established just once. `epa-key-list-mode-map' is the only exception and because there is absolutely no indication that that is justified, we remove this inconsistency. * lisp/epa.el (epa-key-list-mode-map): Set the parent of this keymap while defining it. * lisp/epa.el (epa--list-keys): Do not set the parent of the local keymap here.
Diffstat (limited to 'lisp/emacs-lisp')
0 files changed, 0 insertions, 0 deletions