Jeff Mincy writes:
look at menu-accelerator-modifiers and menu-accelerator-enabled:
menu-accelerator-enabled - Whether menu accelerator keys can cause the menubar
to become active.
menu-accelerator-map - Keymap for use when the menubar is active.
menu-accelerator-modifiers - Modifier keys which must be pressed to get to the top
level menu accelerators.
menu-accelerator-prefix - Prefix key(s) that must be typed before menu
accelerators will be activated.
When I do meta (down&up), the 'file' menu button activates.
It seems to be an input focus issue - maybe WM dependent? (I use
WindowMaker). If the cursor is over the menubar, so that I have the
"arrow" cursor, the menu accelerators do indeed work as you describe.
But if I have the cursor in the buffer area, so that I have the
"ibeam" cursor, pressing and releasing Meta has no effect.
(Of course, if I have to use the mouse to move the cursor up to the
menubar, then it's not much of a keyboard accelerator, is it?)
I also don't understand, although `menu-accelerator-enabled' is set to
nil, why this is working at all? Or do I fail to grok the meaning of
`menu-accelerator-enabled'? (I feel like I'm missing something
here...)
I propose introducing a customizable user variable to truly disable
the menubar accelerators, and that when the accelerators are disabled,
the underlined letters not be shown.
I also propose introducing a customizable user variable to
disable/enable the progress bar.
I will try to find some time to back up these suggestions with
a patch or two...