RE: Bikeshedding go! Why is <M-f4> unbound?

[Drew Adams]

> If a key has a meaning in the environment, even a non-standard
> meaning, users might *expect* the key to keep that meaning even
> when the great and powerful Emacs has keyboard focus.

Understood.  But the same expectation is equally unmet if the key is defined
locally by Emacs.  That part is nothing new.

Emacs can and does change the behavior of some outside keys locally.  In the
case of a few keys it does not on some platforms - typically cannot, IIUC.

Emacs is a local environment, and one that pretty much (i.e., with exceptions)
can give you info about any key.

At the very least (and it seems most are agreed about this), an Emacs user needs
to be able to ask `C-h k' and learn that a given key is (a) defined as Emacs
command `foo', (b) passed-through to Windows, or (c) undefined.