-
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
some keys trigger the FN modifier flag for some reason #10
Comments
I try too bind |
fn + arrow is not possible, because the arrow key-event already implicitly has the fn-flag set. This is a part of macOS keyevents that we can not do anything about, sadly. |
fn + left / right / up / down is translated to home / end / pageup / pagedown respectively by macOS.
@koekeishiya might wanna catch this in code and remap it? |
Ok, I got it, thank you! |
im looking to setup my caps lock key are my primary modifier to control most of chunk via skhd -- is it possible to use capslock as a hyper key somehow? perhaps https://github.com/tekezo/Karabiner-Elements can help otherwise.. |
btw, I just tried it and can confirm that Karabiner Elements is a great combo with skhd. I set caps lock to my hyper key via https://gist.github.com/lunelson/69d041356f90bc0974e22d2a1fb0b059 and now, I can control everything with caps lock as my mod key unfortunately its not perfect though, as you can't create a modifier combo of: |
Events triggered by keys such as all function keys (f*), and the arrow keys have the fn modifier flag set for some reason, even though the fn modifier is not pressed. The same is true even with the mission control option "Use F1, F2, etc keys as standard function keys".
It is tedious to have to manually specify fn as a modifier in these binds.
An option is to automatically flag binds using these literals with the fn modifier during parsetime,
however this could make it unclear to the users that these literals CAN NOT be used with fn as a modifier. e.g:
alt - left
andfn + alt - left
are equivalent.The text was updated successfully, but these errors were encountered: