diff options
| author | jems-lee <30412555+jems-lee@users.noreply.github.com> | 2020-06-14 12:49:36 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-15 02:49:36 +1000 |
| commit | 294cfd8d33aea0b2846fd57c0fdfb6475e093c98 (patch) | |
| tree | 3613095562639b85bf00beec91e880ab672132f1 | |
| parent | 622e94c6cdf6a307ee87b6add974def647979f15 (diff) | |
| download | qmk_firmware-294cfd8d33aea0b2846fd57c0fdfb6475e093c98.tar.gz qmk_firmware-294cfd8d33aea0b2846fd57c0fdfb6475e093c98.zip | |
Delete trailing period in documentation (#9416)
| -rw-r--r-- | docs/feature_leader_key.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_leader_key.md b/docs/feature_leader_key.md index 828d6557d3..0803a411c6 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` in your `config.h`. This sets the timeout for the `KC_LEAD` key. Specifically, when you press the `KC_LEAD` key, you only have a certain amount of time to complete the Leader Key sequence. The `300` here sets that to 300ms, and you can increase this value to give you more time to hit the sequence. But any keys pressed during this timeout are intercepted and not sent, so you may want to keep this value low. . +2. Include the line `#define LEADER_TIMEOUT 300` in your `config.h`. This sets the timeout for the `KC_LEAD` key. Specifically, when you press the `KC_LEAD` key, you only have a certain amount of time to complete the Leader Key sequence. The `300` here sets that to 300ms, and you can increase this value to give you more time to hit the sequence. But any keys pressed during this timeout are intercepted and not sent, so you may want to keep this value low. * By default, this timeout is how long after pressing `KC_LEAD` to complete your entire sequence. This may be very low for some people. So you may want to increase this timeout. Optionally, you may want to enable the `LEADER_PER_KEY_TIMING` option, which resets the timeout after each key is tapped. This allows you to maintain a low value here, but still be able to use the longer sequences. To enable this option, add `#define LEADER_PER_KEY_TIMING` to your `config.h`. 3. Within your `matrix_scan_user` function, add something like this: |