-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Warn in Read Me that inverting fn keys not possible anymore #56
Comments
Oh no I missed this. Thanks for suggesting! I will update the README later. A built-in solution may be (update: @martzell said this doesn't work. I don't have an access to a device to test this. If this doesn't work for you, use 3rd party apps such as Fluor instead):
Make sure to log out and log back in for the changes to take effect. |
defaults write does not work. But Fluor is a great tool too have F1… keys on a per app basis.
And my keyboard system preference pane reverted to normal non-touchbar style, don't know why. No OS X system software update involved.
… On 27. Mar 2020, at 02:55, Ben Zhang ***@***.***> wrote:
Oh no I missed this. Thanks for suggesting! I will update the README later.
A built-in solution may be:
defaults write -g com.apple.keyboard.fnState -bool true
and
defaults write -g com.apple.keyboard.fnState -bool false
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHDEVCG6Q46CY6IJXHCTZHDRJQBQ5ANCNFSM4LMT4UOQ>.
|
Closed by 39ddb49 |
I met the same problem and Karabiner-Elements solved it. If Fluor doesn't work, try this :) |
The checkbox "Use F1, F2, etc. keys as standard function keys" in System Preferences » Keyboard is replaced by Touch Bar options but my MacBook Pro has no Touch Bar. defaults write experiments I've tried did not work.
Workaround: Fluor App. Even better: enables fn invert only for selected apps.
Mac model: MacBook Pro (Retina, 15-inch, Mid 2015)
Mac version (optional): 10.15.3 (19D76)
The text was updated successfully, but these errors were encountered: