qmk-keymap VS qmk_keymap

Yes, it is technically possible in QMK to record a history of the previous 2 keys (or more) to have a skipgram-reducing magic key. This is possible in QMK by saving the keycode for each event in a sliding buffer. See my example on triggering based on previously typed keys and the source for my Sentence Case for implementations of such a key history buffer. I see u/mEFErqlg shared an implementation as well in another comment thread.

I really appreciate all the work that's going into ZMK, and am by no means an expert on the limitations or architecture that they're working within, but personally feel that the recent macro-parameter implementation fails to elevate the Behavior[3] into a sufficiently powerful construct. I'm trying to imagine how it could offer greater composition and control over an invoked sequence of keycodes, key-positions, and behaviors, but if that ever comes to be, it will be on the shoulders of giants. Development has been very active, and the contributers have all done great work. Shoutout to zmk-nodefree-config[4] and thumbkey[5] for android, which has also been under rapid development from a wide group of contributers (special thx to WadeWT and sslater11, amoung many others).

[1]: https://github.com/getreuer/qmk-keymap/

Check out my keymap. My intention is to put a rather light load on the thumbs. Lately I've been doing this:

Uses getreuer's 400 entry autocorrect dictionary. https://github.com/getreuer/qmk-keymap/blob/main/features/autocorrection_dict_extra.txt

A cool thing with QMK is that you may insert arbitrary C code to handle key events. That's a lot of power, and I've been having fun with that. Check out my keymap. Some gems:

Please pull or re-download getreuer/qmk-keymap to get the latest.

I am a software engineer and use a 65% as my daily driver. 65% is enough for the most common keys including a number row on the a base layer, and I have special symbols and F-keys on a symbol layer (see my keymap). For me, the point of mechanical keyboards is ergonomics, and on that front I suggest a split, columnar keyboard with QMK or other programmable firmware. Here is a brief features tour of why I think these keyboards are so awesome.

I'm a software engineer and naturally spend a lot of my time at the computer writing code, plus quite a bit of non-code writing (emails, reviews, ...). Since RSI is something of an occupational hazard, mechanical keyboards are for me mainly about preventative ergonomics and comfort. Though, writing custom code within QMK keymap has interesting productive possibilities... I've been having fun with that.

You want fun experimental features?—check out my QMK repo =)

That's extremely reductive. I rely on the OS for the language support, just like I rely on the OS to understand the USB protocol. It's an inherent part of how a keyboard works. I use tons of other mapping features that are best implemented keyboard-side, including but not limited to:

I hate having to wait for any delays, so I prefer using explicit layer-switching keys, and have configured things so that I'm never tripped up by a timeout or whatever. https://github.com/henrebotha/qmk_keymap

You'll need one or more variables to track things like when you pressed the key. See my map for an example of how to do timing-based stuff using a custom keycode. My use case is quite different to yours (though it's incidentally also related to task-switching!), but you should be able to see how I check for my custom keycode, how to record the time at which something should happen, etc. (Search the file for mentions of KC_TASK.)

I implemented a Tmux layer that automatically prepends the Tmux prefix before every key. It saves one keystroke if you do a single Tmux command, and 2N+1 for N consecutive Tmux commands. https://github.com/henrebotha/qmk_keymap