Re: We need unbind function (was Re: [PATCHES] awaiting...)
On Mon, May 24, 2004 at 06:53:02AM +0900, TAKAHASHI Tamotsu wrote:
> > > Wouldn't this remove the ability to disable an entry from generic in a
> > > specific menu?
>
> Yes, this removes the ability. That's one of solutions for bug#1880.
> Search for "noop" in manual.txt. The manual says that
> "The special function noop unbinds the specified key sequence."
> And it DOES NOT say "noop for index disables an entry from generic
> in index menu." So, I think "noop" should not disable, but unbind, keys.
> So, this won't be a bug if this is included in mutt. But....,
>
>
> > > bind generic f something
> > > bind index f noop
> > >
> > > to bind f to something everywhere except in the index.
Currently "noop" disables the key, as a useful side
effect of the bug#1880. But we should fix bug#1880.
If you want to disable "f" key, you can do:
macro index f <0>
while <0> key is not bound to any function on index
by default.
So, solutions we can choose are:
(1) Include my simple patch. (This is the most
conservative way. Almost nothing changes)
(2) Include dgc's excellent "unbind" patch. (This
provides the most intuitive UI (and many changes))
(3) Document that "noop does not unbind the key. It
does disable the key. You are not able to unbind
the key." (This is the most useless idea.)
--
tamo