[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Óscar Fuentes
Subject: Re: Bikeshedding go! Why is <M-f4> unbound?
Date: Tue, 18 Jan 2011 13:58:07 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

grischka <address@hidden> writes:

>> This is unnecesary. The Windows event loop coded into Emacs already
>> receives Alt-F4 in a single event. What is needed is to determine from
>> that event loop if there is a binding for Alt-F4 (created with *-set-key
>> etc). Once we know that there is no such binding, it is trivial to send
>> back the Alt-F4 event back to Windows.
> Well, it would be difficult to determine on the Windows level whether
> the single keystroke was maybe part of C-x M-f4 or C-h M-f4.  So in
> any case it is better to reuse emacs central event parser.

This is unnecesary too. Alt-F4 must work irrespectively of the prefix
keys typed so far: if you type C-x or C-h and then click on the Close
button on the top right of the frame, Emacs thinks you want to exit the
application. Alt-F4 must have the same effect as clicking that button
(when M-f4 is unbound on Emacs, hence the need for checking the binding
from the Windows event loop).

> To make some suggestion that could work:  Store the key-code in a
> variable like this:
>     case WM_SYSKEYDOWN:
>         last_syskey_code = wParam;
>         ...
> define keys emacs-wise like this:
>     (global-set-key [M-f4] 'w32-syskey)

If we go that route why not just bind M-f4 to a function that closes the
current frame, as suggested at the beginning of this thread?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]