varl/qmk_firmware
1
0
Fork 0
forked from forks/qmk_firmware
Code Pull requests Activity
qmk_firmware/keyboards/kc60/keymaps/noroadsleft/readme_ch1.md
James Young 95309e9af5 [Keymap] Updates to noroadsleft keymap for KC60 (2019-11-05) (#7265) 
* 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
2019-11-05 22:12:21 -08:00

1.8 KiB
Raw Blame History

@noroadsleft's KC60 keymap

Layer 0: QWERTY - _QW

Standard QWERTY layout, with four QMK features:

  • The Menu key has been replaced by MO(_FW), which moves to my Windows Fn layer when held.
  • The Right GUI key has been replaced with a MO(_MA) key, which moves to the Macro layer when held.
  • The Caps Lock key has been replaced with a dual function LT() key, which opens the Windows Fn layer when held, and is Caps Lock when tapped
  • The Left Control key has been replaced with a MT(MOD_CTRL, KC_GRV) key, which is ` ~ when tapped and Ctrl when held.

QWERTY layer

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.

Hardware Dvorak layer

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.

Hardware Colemak layer

Next Chapter: OS Overlays