Mutt version:

Mutt 1.0.1i (2000-01-18)

Is this a bug?
==============

generic binding seems to be broke. Am I doing something wrong?

bind generic j previous-entry
bind generic k next-entry
bind index j noop
bind index k noop

When I hit 'k' or 'j' in the index, it gives me a "Key is not bound."
error.  Yet, when I go to the binding listing screen (by hitting '?'),
'j' and 'k' show up in the generic bindings section as bound to the
functions I assigned.

Something else
==============

While I'm bringing this up -

It'd be nice if I didn't have to do a 'noop' for the same key multiple
times (for the reoccuring menu-specific bindings) , just so that my
generic binding can apply to those menus. It kind of defeats the
purpose of generic bindings in my opinion. I can't reliably set up a
key to work in multiple menus with one command. I understand the
advantages of menu-speicif coverriding generic bindings. I'm just
wondering if perhaps there's some middle ground, like a way to 'force'
a generic binding into any menu.

Thanks for listening.

- Larry

Reply via email to