qmk_distro_msys VS qmk_firmware

- QMK MSYS: you'll need it for many things, for compiling your firmware file and for flashing, especially if flashing with QMK Toolbox isn't permitted in firmware settings (in this case QMK Toolbox just won't recognize your keyboard);

You don't need the GUI though, you can write the simple code yourself, then using QMKMSYS you can compile these flat text files into firmware. Using the appropriate flashing software for ypur microcontroller, you then flash this firmware onto your keyboard.

First, install QMK MSYS from here. Once installation is finished, DO NOT DO "QMK SETUP". I will explain this later.

Download QMKMSYS.exe from https://github.com/qmk/qmk_distro_msys/releases/tag/1.7.2

QMK MSYS: What we will be using to compile the firmware

You don't really need to be able to program though. (Assuming you use Windows) QMK MSYS will help put all the QMK code on your PC and make it ready to make the firmware file, you will just specify which keyboard make & model you have, edit the file line that controls the timing behaviour, and your PC will build the firmware. Then the Toolkit GUI app will help you sync that onto the keyboard.

Download and install latest version of QMK MSYS

a) Installed git for windows. (If you don't know how to use it - don't go this way. Just download qmk-vial as ZIP, extract in "C:\Users\URUsername\qmk_firmware\vial-qmk", install QMK MSYS. Run it from shortcut in installed folder, run "qmk setup -H C:\Users\URUsername\qmk_firmware\vial-qmk" and change directory "cd C:\Users\URUsername\qmk_firmware\vial-qmk" for next steps.) b) Had an error with gh, so installed cli. Cloned qmk-vial with github desktop in the end. c) Had an error with "make", so installed it and cloned submodules. d) Still had an error with "make" when compiling fw "No rule to make target".

Callum's README

For sub-40% keyboards, home row mods like in Miryoku or a modifiers on layers like in Callum in combination with layers, combos etc. are necessary to fit all of the keys needed.

I'm pretty sure, that every sub 40% user has been there once. It's just so wild when you're new to it. Here's my overly long and boring take on the subject. My journey was building a handwired monoblock split I designed for having 6x4 halves with 3 additional keys in the middle - think preonic, but slightly angled halves with pinky columns staggered and 3 keys in the space between the halves. At first my layout was mimicking the regular 60%. I only used layers for numbers, symbols, f-keys and nav cluster. Pretty much like a 60% with a few thumb keys instead of big f***n' useless spacebar. I thought there's no way to comfortably use my keyboard without it. I used to press Control with the inside of my palm instead of contorting my pinky. It was... amazing! Compared to row staggered layout, the ergonomics we're f***ng stellar, man! Little did I know how much can be improved. I was using this layout for about 6 months before I decided to make any big changes. First thing was removing the keys I pressed with my palm. Once I moved heavily used mods to my thumbs, I felt like a superhuman. A bit of muscle memory fighting, but it felt really great not to move my hands towards the lower corners of the keyboard. Once my head started going on and on about the layout, about two weeks later went the number row. I put the numbers on the home row and still keep it that way. It was a huge leap, because it meant now I'm using layers so much more and we're getting into the so-called "minimal" territories. The last step for me was removing the outer pinky columns. I really didn't want to give up tab, backspace and shift on the left side, and I was really opposed to the idea of tap-dancing, combos and other stuff that turns my keyboard into an arcade game. I didn't want to perform an MK Fatality combo every time I need to close a tab in my browser, but what spoke to me was callum layout. No combos, no timing, no double-tapping. Just simple momentary toggle layers turned out to be just what I needed. I have a couple of additional keys, so I use one for mod layers. That way with 4-key thumb cluster I have all I need and so far I am happy. ...until the optimisation mania comes back.

Have a look at Callum style layers https://github.com/callum-oakley/qmk_firmware/tree/master/users/callum

one shot mods – ex. callum, seniply

Not without building it from source yourself. See https://github.com/callum-oakley/qmk_firmware/tree/master/users/callum for a fully baked implementation of what you want. Look at the "swapper" documentation and code.

If not HRMs, how about Callum-style mods? Callum Oakley's keymap works with exactly 34 keys as it turns out.

This feature is called Swapper and you can find a simple implementation here.

Miryoku relies on mod-tap, which some people aren't a fan of. The most common alternative approach are those systems that use sticky (OSM) keys, such as Callum or my own system, Seniply.