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

[Drew Adams]

> > On Windows: `C-h k M-<f4>' => "<M-f4> is undefined" (and 
> > the key does not appear in the `global-map', at least).
> 
> Which means that Emacs actively shadows the default binding on w32.
> Why should Emacs do that?

Why shouldn't it?  Should Emacs not "actively shadow" `C-c' or `C-d' or ... when
launched from a shell, because those keys mean somthing to the shell?

Since when should Emacs simply reflect outside key bindings?  It can, of course.
And perhaps it should in some particular cases.  But let's drop the argument
that it must as a general rule.  There is nothing wrong with Emacs deciding to
"actively shadow" any key it wants.  (It might not always be successful, but
that is another problem.)

IOW, there is a decision to be made about this specific key.  Not some general
hand-waving argument about Emacs respecting the outside context (or user
expectations or...).

The question is about _this_ key.