aboutsummaryrefslogtreecommitdiffstats
path: root/docs/feature_leader_key.md
diff options
context:
space:
mode:
authorGravatar dsissitka <me@dsissitka.com>2018-09-16 17:49:20 -0400
committerGravatar Drashna Jaelre <drashna@live.com>2018-09-17 14:38:06 -0700
commit244e1c5a57eecd349c7d88e1af42d1b3467aeafe (patch)
tree7732eafc3270b81ea8aa8bfe10960958724269b7 /docs/feature_leader_key.md
parent3f680a93eb38408d1fc6b0c78ee94b542cbc7aee (diff)
downloadqmk_firmware-244e1c5a57eecd349c7d88e1af42d1b3467aeafe.tar.gz
Fix LEADER_KEY docs.
LEADER_KEY needs to be set in config.h, not keymap.c. Credit goes to @randywallace for figuring this one out: https://github.com/qmk/qmk_firmware/issues/2514#issuecomment-384847485
Diffstat (limited to 'docs/feature_leader_key.md')
-rw-r--r--docs/feature_leader_key.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_leader_key.md b/docs/feature_leader_key.md
index 0c3f4a133..92aebd463 100644
--- a/docs/feature_leader_key.md
+++ b/docs/feature_leader_key.md
@@ -5,7 +5,7 @@ If you've ever used Vim, you know what a Leader key is. If not, you're about to
That's what `KC_LEAD` does. Here's an example:
1. Pick a key on your keyboard you want to use as the Leader key. Assign it the keycode `KC_LEAD`. This key would be dedicated just for this -- it's a single action key, can't be used for anything else.
-2. Include the line `#define LEADER_TIMEOUT 300` somewhere in your keymap.c file, probably near the top. The 300 there is 300ms -- that's how long you have for the sequence of keys following the leader. You can tweak this value for comfort, of course.
+2. Include the line `#define LEADER_TIMEOUT 300` in your config.h. The 300 there is 300ms -- that's how long you have for the sequence of keys following the leader. You can tweak this value for comfort, of course.
3. Within your `matrix_scan_user` function, do something like this:
```