qmk-keymap VS qmk_firmware

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 =)

The keyboard is flashed with Vial (not Via) compatible firmware, an older version of this.

You could try my QMK firmware. It has 5ms debounce which seems to be good for the vast majority of keybs, but you can always set it higher if you're getting a lot of double inputs...

If you have a GMMK Pro, use this instead of Core: https://github.com/gourdo1/qmk_firmware/tree/PR-branch-Q2/keyboards/gmmk/pro/rev1/ansi/keymaps/gourdo1

Why yes, yes it can... using a 400 word English typo dictionary not to mention a built-in paddle game, a toggle menu that prints out firmware settings to a text editor, mouse control on the keyboard, 24 persistent RGB backlighting effect modes, an overlay numpad, n-key rollover (NKRO), 5ms debounce with 1000ms polling, Win-key lockout for gaming, support for ANSI and ISO layouts and much more...

I'm working on a layout (https://github.com/gourdo1/qmk_firmware/tree/toggles/keyboards/gmmk/pro/rev1/ansi/keymaps/gourdo1) which I am hoping will feature persistent, user-configurable (post compile-time) toggles for certain features.

I have a somewhat more complex setup where there's a gourdo.h file (where my #define's are located) being referenced from my keymap.c, but otherwise, I think I'm doing the exact same thing. Nevertheless, the keycodes don't work when I flash my firmware and I can't figure out what difference is. The problem remains even when I try moving the #define statements to keymap.c itself.