search

BurntSushi / xgbutil

A utility library to make use of the X Go Binding easier. (Implements EWMH and ICCCM specs, key binding support, etc.)
Do What The F*ck You Want To Public License
194 stars 46 forks source link

keybind on "Mod4-<key>" does not always work #42

Closed ayuanx closed 6 years ago

ayuanx commented 6 years ago

It seems you have to press several times to get one successful trigger. I suspect somehow the very first one is always eaten by X window system menu.

BurntSushi commented 6 years ago

I use Mod4-<key> bindings created by this library every day and they work as intended, with no additional keypresses required.

I do not know what a "X window system menu" is.

ayuanx commented 6 years ago

Does your X window start menu pop up when you press Mod4 (aka. super / win)? Mine does.

So in key combinations like Mod4-z, the Mod4 is eaten by start menu. However, if you press and release Mod4 to trigger the start menu popup first, then pressing Mod4-z works.

BurntSushi commented 6 years ago

There is no X window start menu. You clearly have other applications competing for the same key bindings, so this isn't a problem with xgbutil.

On Mon, Aug 20, 2018, 23:47 ayuanx notifications@github.com wrote:

Does your X window start menu pop up when you press Mod4 (aka. super / win)? Mine does.

So in key combinations like Mod4-z, the Mod4 is eaten by start menu. However, if you press and release Mod4 to trigger the start menu popup first, then pressing Mod4-z works.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/BurntSushi/xgbutil/issues/42#issuecomment-414540735, or mute the thread https://github.com/notifications/unsubscribe-auth/AAb34mWwALVr0_01w-cplGT-R2J9HZaiks5uS4LEgaJpZM4WDS1e .