Vikas Agnihotri <[EMAIL PROTECTED]> wrote:
> There seems to be some confusion regarding the 'generic' map.
Indeed. Is "bind generic" just shorthand for "bind pager", "bind
alias", "bind attach"... ? Or is there really a separate generic map,
and mutt thinks "X was just pressed, but X is not bound in the current
map, so let's consult the generic map"? I've been assuming the latter,
and the help screen suggests that there really is a generic map.
> Guess the manual needs to explain all this better.
Even if the manual is improved, the help screen strangeness that Randy
described is also a concern.
By the way, here's what I'm doing that prompted my original comment:
I'm totally redoing all the keybindings. What I really wanted was
something like "unbind_all compose" or "unbind_all *" so I could start
from a clean slate. The next best thing would be "unbind compose X".
Then I could unbind each key listed in the manual to get my clean slate,
and redo each menu separately.
But I can't unbind keys, so for each key I don't to include in a map, I
have to check whether it's bound in the generic map, and if so, bind it
to the same function, otherwise bind it to noop. So if I ever change
the generic map, I have to update all the other maps to stay consistent
with it.
AMC