[Top][All Lists]

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

Re: something is eating C-M-x

From: Stephen Leake
Subject: Re: something is eating C-M-x
Date: Mon, 22 Nov 2021 06:20:38 -0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (windows-nt)

Óscar Fuentes <ofv@wanadoo.es> writes:

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>> I've just installed a new VMWare virtual machine on my Windows box to
>> run Debian.
>> Something is eating C-M-x, so Emacs doesn't see it. Very frustrating
>> when trying to redefine elisp functions!
>> I'm using the LXDE window manager, and I've checked
>> ~/.config/openbox/lxde-rc.xml; that does not define C-A-x.
>> I've searched in various ways for "hotkeys" and similar terms, but have
>> not found what the problem is.
>> Any hints?
>> Is there some X debug program that shows how key events are handled?
> See xev

That shows that C-M-x is being eaten by something; it generates a
KeymapNotify event for the root window, while C-M-s (for example)
generates the expected KeyPress and KeyRelease events.

The docs for setxkbmap hints that perhaps C-M-x is being used to change
between keyboard maps, but "setxkbmap -query" says that's not it.

So there must be some other lowlevel keyboard event mapping going on, by
Debian or something.

> But maybe Vmware itself is eating C-M, which IIRC by default is used for
> releasing keyboard+mouse input.

VMWare does use C-M when not followed by another key to switch to the
host, but C-M-<key> works normally; I use C-M-up to switch windows in
Emacs, for example.

> See menu Edit -> Preferences -> Hotkeys.

That apparently shows the content of the <keyboard> section of
~/.config/openbox/lxde-rc.xml, which I mentioned above; it is an easier
way to see what that file is doing. It does not show a mapping for

> You can remap that key combination or use a special shortcut for
> passing C-M to the guest OS. Search the 'net for "vmware workstation
> control-alt".

I found this page:


Which says that no C-A-key should work, which is simply wrong.

-- Stephe

reply via email to

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