Combo is typicaly used with keys activated together - not a sequence of keys. I have tried using combos on my Gherkin mapping o+p combo to backspace - works great.

Well that explains a lot. When reading the docs I missed this key sentence, “It lets you hit multiple keys at once and produce a different effect.”.

I confess to looking around the docs looking for the per key term setting which the feature Leader Key has.

Thank you @BXO511 for clarifying and the tip on backspacing.

I use the leader key quite a lot, but I don’t like how the leader key itself times out. I hacked it to have an infinite amount of time for the leader key but the normal timeout for the rest of the sequence. This fixes my problems, but I’m curious to know if other users if the leader key will find it useful or not to push the PR a bit further

I’m not sure what you mean by “PR a bit further”. Leader Key has two timing settings that I know of. #define LEADER_PER_KEY_TIMING and #define LEADER_TIMEOUT, both set in config.h. When the per-key feature is set (optional), every key tap beginning with the leader itself resets the remaining time to whatever the timeout is set to. Mine is set to 500 because I felt like anything shorter made me rush. My understanding is that if I have a 3 character trigger plus original leader, I have 2 seconds (500 timeout setting) to complete the sequence before timing out.

Sorry for my lack of clarity. PR means pull request. I’ve open a pull request to QMK to add a new feature to the leader key, but that PR is a bit cold right now, without much comments from the QMK team. If the feature could be useful for other leader key users then I will try make QMK team to accept my pull request.
What the feature does is ignore the timeout for the leader key itself, and the rest behaves equally. So I’m your case you will have an infinite amount of time after pressing the leader key and 1.5 seconds to complete the rest of the sequence. Something like a mix between one shot layers and leader key.
What I want to know if other leader key users find this behavior useful or not.

To me that sounds like a great idea. The leader key could even be on another layer but the leader time kept small. How did you work around the leader key timeout?

I see, I didn’t know that leader keys allow more keystrokes. One shot layers are more akin to sticky keys. I have one set up that allows me to hit F-keys without having to hold down the layer switch key.

I’ve just started to look at oneshot layers and that seems to be a better, cleaner more sensible approach for my needs than combos. Something I’ve realized over the last week is QMK has multiple ways to complete similar actions.

What are sticky keys? I’ve seen those referenced in the docs but no details.

“Sticky keys” are implemented as One Shot Keys in QMK

Sticky keys aren’t just a qmk thing: https://en.wikipedia.org/wiki/Sticky_keys

Well, if you are interested on the technical details, here is the PR: https://github.com/qmk/qmk_firmware/pull/6580

Basically I have edited the leader key feature to ignore the timeout if the sequence is empty, and only starts to count when the sequence is at least one.

Well, I use both and I see room for both. One shot layers are nice, sure, but the leader key allows for more complex interactions/more macros with less keys. Just to put an example, using just one key, on one shot layers you can only create one macro, for that key, using leader key you can create upt to 5 macros with just one key, depending on the number of times you hit that key. Not to mention that is much easier to remember that you hit leader->p->g for ps -ef | grep than to hit layer then the 5th key on the third row.

1 Like

Thank you for the perspective. Been so focused on QMK for specific project, hadn’t considered for use with terminal. My biggest issue with leader is lack of good leader key. Need custom board with split space bar.

Which do you use more often? Oneshot layers, oneshot keys or combos?

This talks about RSI…exactly why I stumbled into programmable keyboards…elbow pain. Glad to say QMK has reduced that by 99% in a very short time! Thank u QMK.

I don’t use any of them on my Planck. I only use hold and toggle layers. I might use combos on my Gherkin though - something like o+p for backspace.

Yeah I just switched to an ergodox, which is also my first QMK board. I’ve had pain in my wrists and hands for years. Switching to programmer dvoark helped a bit, but thusfar the ergodox is working wonders for me. I programmed it to handle my keyboard layout in firmware, so it even works in RDP sessions! Before, I had to fall back to QWERTY when logging in to a remote system.

How was the conversion from staggered layout to ortho? The Ortho or staggered question is my last big decision regarding programmable boards.

My plans are to build a custom board (staggered or ortho) that is a single unit but split (relieves lots of shoulder pressure), and without angling the keys in any way. Just not sure I can undo years of muscle memory to move to Ortho.

Just yesterday came across the tri layer (raise, lower, adjust) syntax/approach/verbiage, not really sure how to describe it. Is this a Planck thing or QMK thing?

@danielo just read some of the comments on this link. Much of what I read is beyond my skill set but it looks like this change is going to happen. Nice job, fingers crossed.

Tri layer can be used with any QMK based keyboard it’s not Planck specific.