-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keybinding with F* does not work anymore #9
Comments
This is likely related to #8, and not the cleanup that came after. |
Confirmed this is related to the fn key. By default on MBP, the function keys are gated by the fn modifier. Thus, to bind a function key, you need to do the following: The sample bind above works fine. Now having to press fn every time to use a function key is annoying, so I assume you have enabled the "Use F1, F2, etc. keys as standard function keys" option in Keyboard settings. This option causes the system to silently add the If you want |
Ah, cool, fair enough. I'll update and change my configs as soon as I have some time. |
See #10 for proposed solution. |
I can confirm, everything works fine adding the "fn" modifier. |
The latest version automatically supplies the fn flag for key-literals that have this set implicitly. |
Does it also work if I have the fn modifier set in my config or should I remove it? |
That will work just fine as well. |
Cool! Thanks |
Hello,
after the cleanup you did, all my keybinding using F* are not working anymore. I usually move through desktops with cmd + f[1-8] and they stopped working when I switched from stable 0.0.8 to HEAD.
I think there has been a regression. 0.0.8 works fine.
If I start HEAD version, the keystrokes are printed on the terminal. It seems skhd is not able to grab the keybinding when f* is involved.
If I change the keybinding to use numbers, like cmd + [1-8], everything works properly also with HEAD version.
The text was updated successfully, but these errors were encountered: