vim-clutch VS qmk_firmware

You mean something like this?

https://github.com/alevchuk/vim-clutch

Just wait until someone shows him vim-clutch.

Une pédale d'embrayage pour vim: https://github.com/alevchuk/vim-clutch

I used the same idea when setting up long-range WiFi (couple of KMs) via antenna for a mesh network.

In order to get the best latency/bandwidth, you need to point the antennas with precision at each other, and in order to know if you're pointing it right, you need to run some tool on a display at the same time, like `ping`, and see when it gets lower when you're pointing it right.

So rather than having to look with one eye towards the horizon, and one eye on a screen to see a tiny number (which I found impossible), I made a quick script that outputs a beep each time ping returns output, with the frequency being higher when the latency got lower. So now I could focus solely on the horizon while using my ears to hear if I was getting in the right direction.

Lots of fun, super useful and makes me wonder (just like you) what other tooling we could use more senses with, rather than just our eyes.

Similar vain: the vim foot pedal: https://github.com/alevchuk/vim-clutch

Im thinking about an improvement, where instead of pressing modifier keys, you simply use 2 vim clutches one for the row above and one for the one below

About two weeks ago, I posted a picture here about a vim clutch (a.k.a. vim pedal) that I got as a present from a friend. Its function is very simple: when you press the pedal, it types i and takes you to insert mode. When you release it, it types ESC and you are back in normal mode. Under the post, fellow redditors started to discuss whether it makes sense for the pedal to type i? Most people were guessing that o and a would be used much more often. I thought, "hey, why don't I just measure it for a couple of days and create statistics about it?"

I only use keyboards running QMK or ZMK, so:

My Caps Lock key is a Control/Escape key (when tapped it behave like a Escape, when hold it's Control), and my left Control is a one shot layer switch key [1], which means I tap LCtrl once, and then press Caps Lock + 5 to get Ctrl+F5. Doable with single hand and more ergonomic as I have an unusually small hand.

[1] https://github.com/qmk/qmk_firmware/blob/master/docs/one_sho...

I agree that reduced finger movement is a crucial step in achieving typing efficiency. This is nicely solved by mod tap modifiers in QMK/ZMK[1] where key acts as a char when tapped and as a layer while pressed.

[1]: https://github.com/qmk/qmk_firmware/blob/master/docs/mod_tap...

Separate wireless controller, see the glue code at [0]

[0]: https://github.com/qmk/qmk_firmware/compare/master...nuphy-s...

If you have a keyboard that runs QMK firmware[0] with the VIA[1] feature enabled[2], then there is a convenient testing app available from the same place you customize your keys [3].

[0] https://qmk.fm/

I made a layout that I'm happy with. Spanish is my native language, so it has characters like the accents and 'ñ', but it's meant to be used for programming as well. Visual Studio uses a lot of Ctrl and Ctrl + Shift shortcuts, so I left them in the same place as the default Corne layout so I can press them both with my pinkie finger. Perhaps some of the ideas are useful to you.

Also, it would be possible to do this for the RP2040. However, it needs some work to get working. but for example: https://github.com/qmk/qmk_firmware/pull/20999

Ok, it's an ST7735, not too different from the ST7789. You should be able to get running by looking at their files in the QMK repo and going from there. You should also check their resources page.