This page covers questions people often have about keymaps. If you haven't you should read Keymap Overview first.
See Keycodes for an index of keycodes available to you. These link to more extensive documentation when available.
Keycodes are actually defined in common/keycode.h.
There are 3 standard keyboard layouts in use around the world- ANSI, ISO, and JIS. North America primarily uses ANSI, Europe and Africa primarily use ISO, and Japan uses JIS. Regions not mentioned typically use either ANSI or ISO. The keycodes corresponding to these layouts are shown here:
Sometimes, for readability's sake, it's useful to define custom names for some keycodes. People often define custom names using
#define. For example:
#define FN_CAPS LT(_FL, KC_CAPSLOCK)#define ALT_TAB LALT(KC_TAB)
This will allow you to use
ALT_TAB in your keymap, keeping it more readable.
QMK has two features, Bootmagic and Command, which allow you to change the behavior of your keyboard on the fly. This includes, but is not limited to, swapping Ctrl/Caps, disabling Gui, swapping Alt/Gui, swapping Backspace/Backslash, disabling all keys, and other behavioral modifications.
As a quick fix try holding down
Backspace while you plug in your keyboard. This will reset the stored settings on your keyboard, returning those keys to normal operation. If that doesn't work look here:
The key found on most modern keyboards that is located between
KC_RCTL is actually called
KC_APP. This is because when that key was invented there was already a key named
MENU in the relevant standards, so MS chose to call that the
Use keycode for Print Screen(
KC_PSCR) instead of
KC_SYSREQ. Key combination of 'Alt + Print Screen' is recognized as 'System request'.
See issue #168 and
Somewhat confusingly, there are two "Power" keycodes in QMK:
KC_POWER in the Keyboard/Keypad HID usage page, and
KC_PWR) in the Consumer page.
The former is only recognized on macOS, while the latter,
KC_WAKE are supported by all three major operating systems, so it is recommended to use those instead. Under Windows, these keys take effect immediately, however on macOS they must be held down until a dialog appears.
Solves my personal 'the' problem. I often got 'the' or 'THe' wrongly instead of 'The'. One Shot Shift mitigates this for me. https://github.com/tmk/tmk_keyboard/issues/67
Modifier keys or layers can be stuck unless layer switching is configured properly. For Modifier keys and layer actions you have to place
KC_TRANS on same position of destination layer to unregister the modifier key or return to previous layer on release event.
This feature is for mechanical lock switch like this Alps one. You can enable it by adding this to your
#define LOCKING_SUPPORT_ENABLE#define LOCKING_RESYNC_ENABLE
After enabling this feature use keycodes
KC_LSCR in your keymap instead.
Old vintage mechanical keyboards occasionally have lock switches but modern ones don't have. You don't need this feature in most case and just use keycodes
See the Unicode feature.
Unlike most Fn keys, the one on Apple keyboards actually has its own keycode... sort of. It takes the place of the sixth keycode in a basic 6KRO HID report -- so an Apple keyboard is in fact only 5KRO.
It is technically possible to get QMK to send this key. However, doing so requires modification of the report format to add the state of the Fn key. Even worse, it is not recognized unless the keyboard's VID and PID match that of a real Apple keyboard. The legal issues that official QMK support for this feature may create mean it is unlikely to happen.
See this issue for detailed information.
You can know which keycodes are supported in OSX from this source code.
usb_2_adb_keymap array maps Keyboard/Keypad Page usages to ADB scancodes(OSX internal keycodes).
IOHIDConsumer::dispatchConsumerEvent handles Consumer page usages.
Japanese JIS keyboard specific keys like
ひらがな(hiragana) are not recognized on OSX. You can use Seil to enable those keys, try following options.
Enable NFER Key on PC keyboard
Enable XFER Key on PC keyboard
Enable KATAKANA Key on PC keyboard
Karabiner - Keymapping tool on Mac OSX - ignores inputs from RN-42 module by default. You have to enable this option to make Karabiner working with your keyboard. https://github.com/tekezo/Karabiner/issues/403#issuecomment-102559237
See the Grave Escape feature.
KC_EJCT keycode works on OSX. https://github.com/tmk/tmk_keyboard/issues/250 It seems Windows 10 ignores the code and Linux/Xorg recognizes but has no mapping by default.
Not sure what keycode Eject is on genuine Apple keyboard actually. HHKB uses
F20 for Eject key(
Fn+f) on Mac mode but this is not same as Apple Eject keycode probably.
TO BE IMPROVED
real_mods is intended to retains state of real/physical modifier key state, while weak_mods retains state of virtual or temporary modifiers which should not affect state real modifier key.
Let's say you hold down physical left shift key and type ACTION_MODS_KEY(LSHIFT, KC_A),
(1) hold down left shift: real_mods |= MOD_BIT(LSHIFT)
(2) press ACTION_MODS_KEY(LSHIFT, KC_A): weak_mods |= MOD_BIT(LSHIFT)
(3) release ACTION_MODS_KEY(LSHIFT, KC_A): weak_mods &= ~MOD_BIT(LSHIFT)
real_mods still keeps modifier state.
without weak mods,
(1) hold down left shift: real_mods |= MOD_BIT(LSHIFT)
(2) press ACTION_MODS_KEY(LSHIFT, KC_A): real_mods |= MOD_BIT(LSHIFT)
(3) release ACTION_MODS_KEY(LSHIFT, KC_A): real_mods &= ~MOD_BIT(LSHIFT)
here real_mods lost state for 'physical left shift'.
weak_mods is ORed with real_mods when keyboard report is sent. https://github.com/tmk/tmk_core/blob/master/common/action_util.c#L57