RE: customizing key definitions with Customize

["Drew Adams" <drew.adams@oracle.com>]

> >     I can see some use value in not always presenting a user, by
> >     default, with a complete keymap to customize. That's all. That
> >     doesn't mean we couldn't also provide a way for a user 
> >     to go ahead and customize the whole keymap. I'm thinking of
> >     user convenience and possible confusion.
> >
> > Perhaps you are right.  I think that the first task is to define the
> > mechanism so it can implement both modes.  Then we could 
> > decide which of the two modes should be the default.
> 
> The problem with customizing the whole keymap is that it should shake
> the modifications out and store just the difference against 
> the default map.  Otherwise, any modifications of the defaults by the
> package authors will not picked up.

I agree with what each of you has said here.

> Also we use the keymaps to store toolbar and menubar data, and we do
> that in a precomputed manner.  That's not something we want 
> to throw at the user by default.

I'm not sure I understand completely what you mean, but I think I agree with
that also. I do think, though, that it will be good, in general, to be _able_ to
let users customize menu bindings for at least some keymaps.