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

[Gregory Heytings]

> > The proposal is only to create a key space in which third party 
> > packages could automatically create global key bindings, without 
> > conflicting with Emacs core (that is, without rebinding any key bound 
> > in vanilla Emacs) and without conflicting with users' personal 
> > settings.
>
> No, your proposal was not _only_ to do that.
>
> _My_ proposal was to do that, and to do it for keys that are not already 
> bound by default - just reserve those for 3rd-party code.

... and two maintainers replied to that proposal that they will never 
agree with it.  Again, it would be better to take that as a postulate for 
further reflection.

> _Your_ proposal was to change some key that already has a default 
> binding, and give it -- and ONLY it -- to 3rd-party libraries as a 
> prefix key.

Yes, that's what "to create a key space" means.

It's a compromise between "being free to reclaim any key at any time" and 
"being constrained to not use any key it doesn't yet use".  IOW, it's a 
compromise between "keeping all keys" and "giving away all unbound keys". 
The compromise is to give away one or two keys, and to keep the other 
ones.  Such a compromise would give as much freedom as possible to Emacs, 
as much freedom as possible to third-party libraries, without changing 
users' habits too much.