Karabiner-Elements: F-keys don't work when Karabiner-Elements is running on Mac Sierra

After much trial and tribulation I got this working as I wanted reliably now on a MacBook with a blasted Touchbar. The function keys are available and working in my programming applications where I want them! Here is pretty much the only setup I could get to work. Hope this helps someone:

Turns out, all I had to do is check ‘Use all F1, F2, etc. keys as standard function keys’. Now F keys work as F keys!

I tried removing that section, as you can see my json file above, it didn’t work, I’m afraid… (I’m not using an external keyboard) Important to mention that I have the new MacBook pro with the touch bar, if that’s relevant.

Seems like Karabiner is still not usable for any developer on any MAcbook with Touchbar since there is no solution so far for this issue. Would like to be corrected of wrong 😃

What worked for me was when I removed all “fn_function_keys” { … } sections in the karabiner.json. The issue i was having was that the touchbar didn’t show when I pressed the fn-key. I also have an external keyboard that F-keys didn’t work, but I can’t test it at the moment, hopefully this solved it!

After much trial and tribulation I got this working as I wanted reliably now on a MacBook with a blasted Touchbar. The function keys are available and working in my programming applications where I want them! Here is pretty much the only setup I could get to work. Hope this helps someone:

I don’t know why it’s marked as closed but this guy is a hero. When I already decided that it’s a snowball’s chance in hell to make it work, the weird combination of unrelated checkboxes above did the miracle.

Mojave 10.14.6 Karabiner-Elements 12.9.0

Not really fixed, I’m afraid - basically, any Shift-F1/… or (any modifier key combo, such as Ctrl/Cmd/Alt) will not work…

1. Sierra 10.12.6
2. Karabiner-Elements 0.91.16
3. “Use all F1, F2, … as standard functions keys” option - both check on and off (didn’t help).
4. Deleted “fn” settings from JSON file:

{
    "global": {
        "check_for_updates_on_startup": true,
        "show_in_menu_bar": true,
        "show_profile_name_in_menu_bar": false
    },
    "profiles": [
        {
            "complex_modifications": {
                "parameters": {
                    "basic.to_if_alone_timeout_milliseconds": 1000
                },
                "rules": []
            },
            "devices": [],
            "name": "Default profile",
            "selected": true,
            "simple_modifications": [
                {
                    "from": {
                        "key_code": "caps_lock"
                    },
                    "to": {
                        "key_code": "escape"
                    }
                },
                {
                    "from": {
                        "key_code": "right_option"
                    },
                    "to": {
                        "key_code": "left_control"
                    }
                }
            ],
            "virtual_hid_keyboard": {
                "caps_lock_delay_milliseconds": 0,
                "keyboard_type": "ansi"
            }
        }
    ]

Same here, still having this issue and it’s really frustrating. Would like to use karabiner-elements but don’t see being able to forgo using function keys.

I’m still experiencing this issue. For the life of me, I can’t get my F-keys to act like regular F-keys on my Kinesis Freestyle2 Blue. I would think there would be a preset that does this (a Complex Modification maybe?). This is really frustrating.

I’ve tried to manually do

                    "simple_modifications": [
                        {
                            "from": {
                                "consumer_key_code": "display_brightness_decrement"
                            },
                            "to": {
                                "key_code": "f1"
                            }
                        },
                        {
                            "from": {
                                "consumer_key_code": "display_brightness_increment"
                            },
                            "to": {
                                "key_code": "f2"
                            }
                        },
                        {   
                            "from": {
                                "consumer_key_code": "play_or_pause"
                            },
                            "to": {
                                "key_code": "f6"
                            }
                        },
                        {
                            "from": {
                                "consumer_key_code": "mute"
                            },
                            "to": {
                                "key_code": "f8"
                            }
                        }
                  ]

It seems to work alright for f6 and f8, but not for remapping brightness to f1 and f2. It seems like something might be wrong with my syntax, because I’m seeing this:

This has been fixed - thank you!

On Thu, Oct 27, 2016 at 10:19 AM, Szabolcs Kurdi notifications@github.com wrote:

Why can’t this “feature” be turned off? With the newest update I got a Function keys tab, but no matter what I set there, it’s wonky 😦

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tekezo/Karabiner-Elements/issues/274#issuecomment-256711174, or mute the thread https://github.com/notifications/unsubscribe-auth/ABRIPBnvCw2SaOVyEo-ioGeml9zD2oNOks5q4N0egaJpZM4KSYwD .

Is there a “don’t remap apple/internal” option?

The whole point of this (I thought) was to remap other keyboards like Windows/Microsoft. That’s where my F keys don’t work. Remapping F6->F6 does nothing useful.

Edit: Just checked out the master (beta) version and I know what you’re talking about now. The F keys were being remapped to vol up/down etc on Windows also, but that is fixed now.