From c80c37fd8750289857db259e0c6dab80c5e9092e Mon Sep 17 00:00:00 2001 From: Josh Klar Date: Sat, 25 Aug 2018 11:36:59 -0700 Subject: [PATCH] Additional, updated documentation --- docs/feature_leader_key.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/feature_leader_key.md b/docs/feature_leader_key.md index 233f68f7d629..0967d6e17f59 100644 --- a/docs/feature_leader_key.md +++ b/docs/feature_leader_key.md @@ -40,4 +40,10 @@ As you can see, you have a few function. You can use `SEQ_ONE_KEY` for single-ke 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. -If you would rather end the sequence with enter instead of having a timeout, include the line `#define LEADER_MODE` in your config.h and you can take as long as you want. If you want to cancel your action, simply press the leader key again. +If you would rather end the sequence with Enter instead of having a timeout, +include the line `#define LEADER_MODE_ENTER` in your config.h and you can take +as long as you want. If you want to cancel your action, simply press the leader +key again. To reuse an above example, you could type `dds` in any +amount of time to trigger the DuckDuckGo search macro, or `dd` +to cancel partway through. Leader sequences will _not_ auto-trigger without +hitting Enter with `LEADER_MODE_ENTER` defined.