RE: [External] : Re: Experimentally unbind M-o on the trunk

[Drew Adams <drew.adams@oracle.com>]

> I think menus in the typical GUI sense have and even more severe issue
> with limited space than key bindings do. Emacs' file menu includes
> find-file, yet Emacs' key bindings expose all of these variants:
> 
>    C-x C-f         find-file
>    C-x C-r         find-file-read-only
>    C-x 4 f         find-file-other-window
>    C-x 4 r         find-file-read-only-other-window
...

If you say "typical GUI" then yes, typically
menus are limited.

Menus don't have to be.  Just as you can have
zillions of command names, organized however
you like (e.g. those above all have to do with
visiting files, and start with `find-file'),
so you can have zillions of menus and menu
items in a menu tree or forest.

What makes a large command-name space usable
(navigable) is the power of _completion_.

Providing keyboard completion against menus,
even against all parts of menu paths, makes
the potential space of menus just as usable
and navigable - just as large - as that of
command names.
___

If you use library La Carte then you get
completion against entire paths to menu items,
which also means completion against menus at
any level (e.g. show all children of some
submenu).

If you use a completion feature such as
Icicles with La Carte than you can also
match against those paths in any number of
ways (regexp, fuzzy matching, whatever).

These tools also let you type input that
targets a particular menu item directly -
direct access, as opposed to drilling down
bit by bit.
___

https://www.emacswiki.org/emacs/LaCarte

https://www.emacswiki.org/emacs/Icicles