bug#30530: 26.0; Emacs manual: mention (1) user-reserved keys, (2) users can bind any keys

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

> > Drew pointed out that suggesting to bind user reserved keys was almost
> > as if we were binding them.
> 
> I disagree with Drew.  By that logic, no one can ever say anything
> about binding these keys, and they must always remain unbound, which
> of course would defeat the reason for reserving them.

No.  This is about a library - and in particular an
extremely widely used library, perhaps _the most popular_
Emacs library - recommending that users globally bind a
whole set of user-reserved keys to commands for use only
by that library.

And yes that is pretty much tantamount, in practice, to
that library globally binding those keys by default.

Your claim that if a library doesn't suggest that users
sacrifice their reserved keys for that library then _no
user will ever bind such keys_ is, well, preposterous.
That doesn't follow at all.

Talk about "by that logic..."!  The Emacs doc makes clear
that these keys are reserved for users.  Users do not need
a library to instruct them to co-opt the keys for its use.
Without such "help" users will continue, just fine, to bind
such keys for whatever uses they like - as they always have.

For Org to say that for best use/experience Emacs recommends
that you globally bind these N keys to Org commands works
against their reservation for users, as a practical matter.
Some (many?) users, especially newbies, may well blindly
follow such a bogus "best use" recommendation.

I'm surprised that you would endorse this.  There is no
need for it, and it is not helpful.