Re: mutt/2566: changing key mapping does not 'unbind' old mapping
Synopsis: changing key mapping does not 'unbind' old mapping
State-Changed-From-To: open->suspended
State-Changed-By: rado
State-Changed-When: Fri, 24 Nov 2006 16:47:53 +0100
State-Changed-Why:
It is not a bug, changed to feature request, but at the same
time this will probably not be in for a long time,
see reasons below.
**** Comment added by rado on Fri, 24 Nov 2006 16:47:53 +0100 ****
(unnecessary attachment deleted)
With the suggestion not to have a default binding, this makes
mutt depend on an external file, which probably is not desired:
mutt should work out of the box standalone, independent of
potential mistakes by admins put in that file.
And it should provide some _sane_ state to give debuggers
a usable interface and a chance to track back what's wrong
when starting with -n -F /dev/null, again not to rely on a file.
Unbinding old keys to functions to have only the single defined
key to activate a function could be made optional.
I'd like to have this, too! "noop"ing is a PITA. :)