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

[Lennart Borgman]

On Thu, Jan 13, 2011 at 4:59 AM, Óscar Fuentes <address@hidden> wrote:
>
> When Alt-F4 is pressed, the event is sent to the application as any
> other keypress. The application can handle the event as it pleases
> (that's the case of Emacs) or delegate the handling of that event to
> Windows, which performs standard actions for certain well-known
> events. But please note that the event is sent to the application first
> and the OS executes the standard associated action only when the
> application delegates the event handling to it. This differs from KDE,
> which handles Al-F4 and Emacs never sees it
>
> This is the typical event loop of a Windows application (pseudocode):
>
> switch(event) {
> case foo: do_something(); break;
> case bar: do_something_else(); break;
> /* More case's for all events we are interested on */
> ...
> /* Let Windows handle all the rest: */
> default: let_Windows_process_it()
> }
>
> When Alt-F4 is delegated to Windows, it generates events for closing the
> active window.

Good points, but did you verify that it generates an event for closing
the active window (and not for quitting the application as the doc at
MS seems to suggest)?

> On Windows, if the Emacs system menu is activated (you click the icon
> just above the File menu) it shows a standard entry "Close Alt-F4". But
> then you press Alt-F4 and Emacs reports on the modeline "<M-f4> is
> undefined".