diff options
| author | Robert Pluim <rpluim@gmail.com> | 2023-01-19 16:05:45 +0100 |
|---|---|---|
| committer | Robert Pluim <rpluim@gmail.com> | 2023-01-20 15:14:45 +0100 |
| commit | 06953fc8e1d70397f421e1c6efc327af8e0bad6c (patch) | |
| tree | ad69dc279056480e9411d6bbf85577cc29d44600 /lisp/emacs-lisp/memory-report.el | |
| parent | dcd59457b48f1fb115e9847eef1c983406885717 (diff) | |
| download | emacs-06953fc8e1d70397f421e1c6efc327af8e0bad6c.tar.gz emacs-06953fc8e1d70397f421e1c6efc327af8e0bad6c.tar.bz2 emacs-06953fc8e1d70397f421e1c6efc327af8e0bad6c.zip | |
Make `keymap-set-after' work for menus
It still doesn't work for an AFTER that's a key, though, since
`key-parse' produces vectors, and keymaps contain integers.
* lisp/keymap.el (keymap-set-after): Only parse AFTER as a key if it's
a string. For consistency, use `key-parse' on the definition if it's
a string, just like `keymap-set'.
* test/src/keymap-tests.el (keymap-tests--command-3): New dummy command.
(keymap-set-after-menus): New test. Check that we can insert a menu
item after a specific entry.
Diffstat (limited to 'lisp/emacs-lisp/memory-report.el')
0 files changed, 0 insertions, 0 deletions