95309e9af5
* Rename layers_keymap to layer_names * Update Escape and Left Control keys - change KC_GESC to KC_ESC - change KC_LCTL to MT(MOD_LCTL, KC_GRV) * Disable features I don't use Makes the firmware lean. Why? Because I can. :D * Update the readme files * Add KC_F13 through KC_F24 emulation ... and update the readme files accordingly. * Update rules/config - Swap EXTRAFLAGS for LINK_TIME_OPTIMIZATION_ENABLE - remove NO_ACTION_MACRO and NO_ACTION_FUNCTION - Re-enable COMMAND * concatenate full-length and short layer names * enable dynamic macros * update readme files
1.8 KiB
1.8 KiB
@noroadsleft's KC60 keymap
Layer 0: QWERTY - _QW
Standard QWERTY layout, with four QMK features:
- The
Menukey has been replaced byMO(_FW), which moves to my Windows Fn layer when held. - The Right
GUIkey has been replaced with aMO(_MA)key, which moves to the Macro layer when held. - The
Caps Lockkey has been replaced with a dual functionLT()key, which opens the Windows Fn layer when held, and isCaps Lockwhen tapped - The Left
Controlkey has been replaced with aMT(MOD_CTRL, KC_GRV)key, which is` ~when tapped andCtrlwhen held.
Layer 1: Hardware Dvorak - _DV
Accessed by holding either Fn and tapping /? key, then tapping 2@.
A hardware-based Dvorak Simplified layout. At my weekend job, I use a shared computer that runs MacOS Sierra, in US QWERTY layout. In this layer, I can leave the system in QWERTY, plug my keyboard in, and still type in Dvorak.
Layer 2: Hardware Colemak _CM
Accessed by holding either Fn and tapping /? key, then tapping 3#.
A hardware-based Colemak layout. Been thinking of trying it, so it's here.
Next Chapter: OS Overlays