diff options
Diffstat (limited to 'docs/feature_leader_key.md')
-rw-r--r-- | docs/feature_leader_key.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/feature_leader_key.md b/docs/feature_leader_key.md index 46633b287..0c3f4a133 100644 --- a/docs/feature_leader_key.md +++ b/docs/feature_leader_key.md | |||
@@ -39,3 +39,11 @@ void matrix_scan_user(void) { | |||
39 | As you can see, you have a few function. You can use `SEQ_ONE_KEY` for single-key sequences (Leader followed by just one key), and `SEQ_TWO_KEYS`, `SEQ_THREE_KEYS` up to `SEQ_FIVE_KEYS` for longer sequences. | 39 | As you can see, you have a few function. You can use `SEQ_ONE_KEY` for single-key sequences (Leader followed by just one key), and `SEQ_TWO_KEYS`, `SEQ_THREE_KEYS` up to `SEQ_FIVE_KEYS` for longer sequences. |
40 | 40 | ||
41 | Each of these accepts one or more keycodes as arguments. This is an important point: You can use keycodes from **any layer on your keyboard**. That layer would need to be active for the leader macro to fire, obviously. | 41 | Each of these accepts one or more keycodes as arguments. This is an important point: You can use keycodes from **any layer on your keyboard**. That layer would need to be active for the leader macro to fire, obviously. |
42 | |||
43 | ## Adding Leader Key Support in the `rules.mk` | ||
44 | |||
45 | To add support for Leader Key you simply need to add a single line to your keymap's `rules.mk`: | ||
46 | |||
47 | ``` | ||
48 | LEADER_ENABLE = yes | ||
49 | ``` | ||