[Top][All Lists]

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

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

From: Stefan Monnier
Subject: Re: Bikeshedding go! Why is <M-f4> unbound?
Date: Wed, 12 Jan 2011 21:42:11 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

> The proposal was to bind M-f4 to save-buffers-kill-terminal or a
> similar function on Windows installations only.

I think handle-delete-frame would make more sense.

> M-f4 is a standard keybinding in Windows and it normally does the same
> thing as it does in Gnome and KDE, which is close the active window or
> exit the current application. The problem is that when I hit M-f4 in
> *Emacs* running on Windows, Emacs says that the key is undefined and
> that's the end of that.

> Right, but M-f4 doesn't "work" in Windows for a reason that is beyond
> me, but which some people on here seem to understand.

So now the question is indeed: how is M-f4's standard Windows behavior
of closing the window expected to be implemented?  Is it possible to
globally (well, except for Emacs ;-) change this key to some other one?

> This is where the idea of binding M-f4 in Emacs came up. Whether it's
> a good one or a bad one, I don't know...

Maybe binding it (in w32) to handle-delete-frame would be a good way to
implement the expected behavior, indeed.  But first, we need to know how
it's normally implemented in standard confirming applications.


reply via email to

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