qmk_firmware VS ADuck

Oh, it was actually this guy https://github.com/treeman/qmk_firmware/blob/master/keyboards/ferris/keymaps/treeman/repeat.c . I wonder how your implementations differ.

I sure do.

I've made some blog posts about it: https://www.jonashietala.se/blog/tags/t-34/, although they're a bit outdated right now. The source code is more up to date: https://github.com/treeman/qmk_firmware/tree/master/keyboards/ferris/keymaps/treeman

I haven't made a write-up of what I'm currently running, but it's on Github.

I have my own implementation. See repeat.h and repeat.c and how it's used in keymap.c. You can ignore the "reverse repeat", making the implementation quite simple.

Here's a blog post of my layout and here's the current layout in code (which has some smaller changes to the base layer).

This is my current 34-key layout. Some notable features:

This is my qmk keymap and here's a blog post about the keymap (although I've made some changes since then).

I fear, if you want a highly customized layout on a highly customized board, you have to work a little for it ˄˄ But the author put his code on github, so you can start from there: https://github.com/treeman/qmk_firmware/tree/master/keyboards/kyria/keymaps/treeman My tip: use his Kyria version, and just consider which keys will be obsolete, and you can not use. Then try to flash on the Gergoplex.

I can't really call it "my" CAPSWORD, since I got the idea from /u/jonas_h and it looks like several others have contributed to it. That said, it looks pretty easy to extend to handle additional characters by adding extra cases to this switch statement. If you have a continuous range you want to add, you can use the KC_A ... KC_Z syntax. Otherwise, you'd have to add them one per line, but it's still pretty doable.