Re: [CVS] f7, f8 bound..

[Per Abrahamsen]

Miles Bader <address@hidden> writes:

> Per Abrahamsen <address@hidden> writes:
>
>> With your code, the rules are simle:  If you change a keymap with
>> customize, all other changes are lost.  With such a simple rule, the
>> rest of the world can comply.
>
> That's obviously a simple rule, but it's also silly and bad; if that's
> what the current code does, then it's not usable.

Why "not usable"?  

It seems a lot better than what we have now, which is nothing.

Well, it is not usable for the global map, too many packages write to
that, but packages writing directly to mode maps aren't that common.
For the global map, maybe we can get dispensation to use two keymaps.

> Your two variable solution has a similar problem, BTW -- if
> e.g. `custom-global-map' overrides `global-map', and someone has bound a
> key via custom, and tries to re-bind it using `M-x global-set-key' --
> then his new binding will be effectively ignored!

True, I haven't though of using non-customize functions interactively.
They would have had to be modified in order to make the two keymap
solution a 100% solution.  I believe there are very few of those
commands.  This is similar to how Stefan made the global minor mode
function customize aware.