Hotkey using [ cmd + num ] not detected

[matthiasbe]

Hi,
First of all thanks for these awesome projects, I'm a linux fan using an osx at work, I was really looking for a tiling wm 👍

There is something odd with my installation of skhd + chunkwm though, hotkeys [cmd - 1], [ctrl + cmd - 1], and more generally something like [ cmd | ctrl | alt | shift + [ 1 - 9 ] ] is not detected.

I have also tried with & instead of 1, é instead of 2 etc ... without any success.
My keyboard looks like this

I'm on Mojave 10.14.4
I'm using latest HEAD but this didn't work either with the homebrew current build.

Oh it seems it's related to #30

If you would like more information please tell me 😉

[koekeishiya]

Could you try to create a bind by using the keycode instead to see if that works? You can find this by looking at the images in #1 or by using https://github.com/koekeishiya/cev

[matthiasbe]

Replacing cmd + 1with cmd + 0x12works like a charm, thank you 👍

If you want some info about the cause of the aliasing gap, feel free to ask

For those who have the same problem, here is the changes made :

cmd - 1 : chunkc tiling::desktop --focus 1

To

cmd - 0x12 : chunkc tiling::desktop --focus 1

PS : I couldn't get cevto work, I had the message cev: could not create event-tap, try running as root!even if I started the program with sudo cev. Do you want me to post an issue on the appropriate repo ?

[koekeishiya]

Glad the keycode trick worked. I'll take another look at how the keycode mapping table is generated.

PS : I couldn't get cevto work, I had the message cev: could not create event-tap, try running as root!even if I started the program with sudo cev. Do you want me to post an issue on the appropriate repo ?

Not necessary. I plan to add support for this to skhd itself at some point before the next release.

[koekeishiya]

Added support for observing keyevents and outputting keycode/modifier information.
Launch as: skhd --observe or skhd -o. Press ctrl+c to quit.

Edit: Part of release v0.3.3

[koekeishiya]

I actually cannot reproduce this. Closing for now. If someone else experiences the same behaviour we can create a new issue for that.