> > Then \bind "" "shortcut" will override no (no corresponding entry in > > the master bind file), > > This one does nothing.
And I display it in purple so that a user can remove it. After all, the GUI is an interface to user.bind. > > one (but bindfile specific), or failed to > > unbind existing binding(s). This is almost the same as \unbind, except > > that \unbind will unbind a specific lfunc. > > I agree that there may be a problem with overriding prefixes. As I have said, your \bind "" "C-g" is the same as \unbind, but less specific. I consider that as a problem. Using \unbind lfun shortcut, you will not have the problem with overriding prefix, display this item by lfunc, etc. Also, there will be serious trouble in implementation because you can not represent your item properly in a KeyMap (like what unbind_map does). > No, I propose to always show all the lfuns _once_. Then, besides the > lfun, there may or may not be binding(s). If the binding of this lfun > is the same as in master, it is in plain font, otherwise on bold font. > > Below that, we will have to add the lfuns-with-args (at least those > who are bound to something). I see. The only difference I can see now is that 1. I display 'unmatched unbind' in purple, and you dislike it. (You logic CAN NOT display it.) 2. I display bindings seprately so that I can easily remove and revert. You tend to group shortcuts together. The implementation of your proposal is much more difficult. Anyway other specific complaint againt the current GUI? Bo
