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

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

> > > | C-x j         | C-o j         |
> > > | C-x j = f     | C-o j = f     |
> > > ...
> >
> > You don't seem to be hearing that I want _more_
> > than just reserving one prefix key, `C-o'.

... <long reply about why `C-o' shouldn't be changed>

Why that reply to my message?  The point of my
message was simply that we should not reserve _only
one key_ for 3rd party use.  We should reserve more
than one, and the keys to reserve, to start with,
are those that are not yet bound.

I am NOT the one who started all the posts about
which keys already bound by default to reserve for
3rd-party use.  _MY_ proposal was instead to start
by reserving for 3rd-party use all keys currently
_NOT_ bound by default.  That's a completely
different approach.

It's Gregory who made a counter proposal to instead
reserve _only one_ prefix key for that, and also
changed to proposing, for that purpose, that Emacs
give up some key _already bound_.  And down the
rabbit hole we went...
___

I did say, as a _parallel_ idea, that Emacs could
also likely benefit from restructuring of existing
default key bindings.

I made the point that some keys bound by default to
repeatable keys are not used for repeatable commands,
and that their commands could usefully be made
repeatable, or those keys could instead be given to
other commands that are naturally repeatable.

And I made the point (and emphasized it _over_ the
point about repeatable commands) that some keys
bound by default to commands that maybe aren't so
useful overall could usefully be changed to prefix
keys instead.

And I made the point that a fair amount of useful
refactoring could be done by moving some commands
that are currently bound by default to bindings
under prefix keys.

But all of that parallel idea about possible changes
to Emacs default key bindings - refactoring - is
completely separate from the proposal I made about
reserving keys for 3rd-party code.
___

My proposal to reserve all currently unbound keys
for 3rd-party code is what I really argued for.  Any
discussion about changing existing key bindings can
go on and on, contentiously, and it is not urgent.

IMO it is more important to impose a moratorium
_now_ on Emacs grabbing more and more unbound keys
for its default bindings.

And the discussion that's ensued from Gregory's
counter proposal has made it all the more urgent to
do what I proposed.  There are suggestions from
that bindings-changes discussion for Emacs to grab
even _more_ unbound keys for default bindings.

Unfortunately, Gregory's counter proposal took over,
and there's (predictably) been a flurry of back &
forth about this, that, or the other key as a
candidate for repurposing.

I specifically wanted to avoid that.  (But yes,
when discussion about this or that key ensued, I 
occasionally added my 2 cents about the key.)