qmk_firmware VS miryoku

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.

I've seen https://github.com/manna-harbour/miryoku but it doesn't appear to be easily modified.

A 75% keyboard still require quite a lot of wrist movement, which is not ideal in your situation. It's better to learn to use layers, you could still have all the function keys and such with a 36 or 34 keys. With with such a small keyboard you don't need to move your wrist while typing. A Corne or even a Ferris Sweep can do the job with a proper keymap, like Miryoku.

If you prefer to have semicolon on Base you'd substitute custom Base, Nav, and Sym layers, swapping semicolon and slash, with https://github.com/manna-harbour/miryoku/discussions/85.

The Miryoku layout [1] has a dedicated number layer which turns the left half into a number pad. Practical (once you get used to it) and portable.

[1] https://github.com/manna-harbour/miryoku

It's understandable if some people would prefer a larger layout. I wouldn't argue people should be using smaller keyboards.

It's "I don't mind moving my hand to hit the key" vs "I don't mind holding down some Fn key to hit the key". (Or with F1-F12 on Macbooks, you need to both hold down a Fn key and move your hand).

For an example of "36 keys ... how", I think the popular miryoku layout is fascinating. https://github.com/manna-harbour/miryoku/tree/master/docs/re... -- Often, mnemonics for particular keys aren't all that complicated.

Except for those who use Miryoku, which is not optimized for software development, probably every single person here will have its own custom keymap.

The keyboard on the other desk is a wireless Corne low profile kit I built up a while back using a couple nice!nano controllers and their low power display too. For general typing I don't have much of a problem going back and forth between the two, but the Corne is only 34 keys and I use a complex layout called Miryoku to get access to most symbols and functions I have by default on my 360.