keyboard_layouts VS qmk-keymap

So it's possible to have a magic key for same-finger bigrams (SFBs) as seen in Magic Sturdy.

https://github.com/Ikcelaks/keyboard_layouts/blob/main/magic...

Regarding chording, you might find inspiration in the chording schemes in Ikcelaks’ Magic Sturdy, the Ardux project, and precondition's "steno-lite" combos.

Beyond reversing, Ikcelaks's Magic Sturdy layout is a showcase of what else can be done. It is a layout where the Alternate Repeat key is placed in easy reach on the right index finger. This is the "magic" in Magic Sturdy. This key is configured to remove SFBs and type common n-grams, or potentially do anything else you want: "this key can be fully dynamic based on the last key press and need not be constrained to logically reversing that keypress." I've been trying Magic Sturdy for the past few weeks, and definitely this is a fun idea.

I've lately been experimenting with variations on Oxey's Sturdy, which is an attractive layout for an unusually strong combination of low redirects and high rolls, yet keeping SFBs and pinky use low. A very interesting mod that I'm using now is Ikcelaks's Magic Sturdy. It incorporates the Alternate Repeat Key as a "magic" key whose function is determined adaptively based on the previous key. This is leveraged to get around the highest SFBs and as a shortcut to type common n-grams.

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