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

I know you have this working now, but I wanted to share my solution just in case you want it or somebody else does. I tried to paste the code snippets here, but Reddit's editor either does not like me or just sucks in general. I could not get the code formatted correctly and many times it pasted the content more than once. You can find everything at this link: https://pastebin.com/s9ppXFkV. I'll also share the files themselves from my Github, but be forewarned that my keymap and userspace is a mess right now because I've borrowed and modified features from a lot of different places. One day I'm gonna rebuild from the ground up.... This is implemented on a Corne split KB, using examples from the Drop Ctrl and other users who've implemented LED maps. Anyway, first thing I did was create an led array similar to the key matrix in the board files(https://github.com/mwpardue/qmk_firmware/blob/caracarn_develop/keyboards/crkbd/c4/c4.c) Information on this can also be found at https://docs.qmk.fm/#/feature_rgb_matrix Next I created the LED matrix, using the HSV color codes but RGB could be used just as easily, you just have to modify the function so it isn't looking for HSV codes. I use things like NUM_UGL for the underglow color and this is so I can reference the underglow color easily in other locations. #define NUM_UGL HSV_RED (https://github.com/mwpardue/qmk_firmware/blob/caracarn_develop/keyboards/crkbd/keymaps/caracarn/keymap.c) Lastly the function to set the LED colors. There are some extra bits in there, such as not using the LEDMAP on the _BASE or _ADJUST layers, except for the underglow LEDs, so I can use RGB Matrix effects on those layers. There's also some LED behavior defined around xcase and MOD_MASK_SHIFT, but I'm sure you can see the relevant bits from this. (https://github.com/mwpardue/qmk_firmware/blob/caracarn_develop/users/caracarn/features/rgb_matrix_ledmaps.c) If you have any questions please let me know. Sorry for not being able to post the relevant bits directly here, I have a hard time making Reddit's code blocks work right.

Unfortunately even using the file you provided, edited where appropriate, it still doesn't seem to sync to the secondary side. Am I mistaken in either a) how I'm trying to implement in https://github.com/mwpardue/qmk_firmware/blob/caracarn_develop/keyboards/crkbd/keymaps/caracarn/rgb_matrix_ledmaps.c (line 68) or b) thinking that this only needs to sync in one direction?

There may be some modification required, depending on the specifics of the board. Here’s A guide I wrote detailing the things I had to do to make my Corne work. But a non-split kb without OLED screens would probably only have to worry about the 5v jumper for RGB.

I have uploaded my most recent changes to my github, please disregard some of the more odd bits as they still need to be cleaned up. I tried implementing rafaelromao's smart_case but ran into multiple issues so I disabled those changes and will pick it back up this evening on my Preonic. It'd be interesting to get it working but I'd really like to get this shift/oneshot/capsword key working. My userspace is where most of this code resides.

I did finally get my secrets files excluded and everything pushed to github, so if you want to take a look it's at https://github.com/mwpardue/qmk_firmware/tree/master/users/caracarn and https://github.com/mwpardue/qmk_firmware/tree/master/keyboards/preonic/keymaps/caracarn I know it's all a mess right now, my keymap and userspace is essentially a copy of rafaelromao's keymap with a lot of things currently commented out or extraneous bits still floating around. I know the issues I'm having could just be due to some of this extra junk I have in my keymap, so I really need to clean it all up...

My repo: https://github.com/mwpardue/qmk_firmware