RE: [External] : Re: Concern about new binding.

[Gregory Heytings]

> > A proposal to solve the current problem and future similar problems is 
> > to free one of the keys, and to mention in `(elisp) Key Binding 
> > Conventions' that it is, forever, reserved for external packages.
>
> I'm not in favor of that - a single key for all 3rd-party code.
>
> [...]
>
> I'm not in favor of that either - still too limiting.

I'm puzzled.  The proposal frees one complete keymap for libraries such as 
Magit and yours.  With say C-o, Magit could use C-o g and C-o M-g, you 
could use C-o p and C-o / and ..., and so forth, with the guarantee that 
Emacs would never reclaim any key in that map.  That's a lot of room...

> I favor allowing all keys that are currently allowed for 3rd-party code. 
> And I favor Emacs itself implementing a moratorium on binding any more 
> keys by default.

... but apparently you prefer to continue to use the few remaining keys 
that are not bound by default?  Isn't that contradictory?

> To me, that's too limiting for 3rd-party libraries. I'd prefer what I 
> say above.  Emacs itself should keep its hands off new keys.

That's clearly an unreasonable demand.  When new commands are added to 
Emacs, I see no reason to not bind them to some key.  I also see no reason 
to not bind commands that were for one reason or another not bound when 
they were included in Emacs, and are nowadays considered important enough 
to be bound to a key.