qmk-keymap VS CMD-dactyl-manuform

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

Hi I am using this github repo's shcematics: https://github.com/markdhooper/CMD-dactyl-manuform/blob/master/schematics/Schematic_dactyl-manuform-5x7.png

I built a Zodiark with is basically a Soflie but with more keys (68 keys). It's pretty good but I would prefer more thumb keys and LEDs at the top of each key.) I would recommend a Dactyl Manuform. See https://dactyl.siskam.link/manuform and https://github.com/markdhooper/CMD-dactyl-manuform

also thinking of this fork specifically

also i'm thinking of using this fork rather than the regular manuform 5x7, thoughts on it?

So i think ill build this dactyl variant and was just wondering if there is a pro micro with usb c? as long as it is as easy to flash with QMK and has the same amount or more pins

I followed this to build it so it would be close to my moonlander in key configuration: https://github.com/markdhooper/CMD-dactyl-manuform

For the dactyl I used Mark's fork and followed his excellent guide for the Cmd. [CMD-dactyl-manuform:github] https://github.com/markdhooper/CMD-dactyl-manuform [CMD Guide] https://www.youtube.com/watch?v=CxNKWNKBLMs&t=908s

CMD-dactyl-manuform: github

Just when i finished the design i found this tutorial with these stl files and they are more detailed and have the mountingholes unvisible from the outside... so i think im starting my dactyl journey with his tutorial and dodge my own files.

I see the line you're talking about. Didn't pay any attention to it till you pointed it out. I guess that I got confused when looking at the schematic that/guide that I've been following: Schematic