Bazecor VS miryoku

Sadly I agree. Splits are great. I am eagerly awaiting my ortholinear split keyboard from https://dygma.com/ - no affiliation other than being a customer of their first keyboard, the raise and having the defy on order.

Maybe it's just me, but I think the proliferation of mechanical keyboards brings people closer to the fringe where custom keyboards, layouts, parts and pcbs are the norm for the pursuit of perfection.

Windows | Mac Arm | Mac Intel | Linux

The software is open-source and you can fork it if you want. Here's the link to our Github: https://github.com/Dygmalab/Bazecor 😊

I have tried passing the disable shm flag without any luck (disable-dev-shm-usage). The repo is https://github.com/Dygmalab/Bazecor/tree/blacksmith

Dygma Raise or Defy.

Bazecor 1.1.2 Firmware v1.0.9beta

This bug is still not fixed after 2 years and it's very disappointing. I use OSL for almost all layers except for macro layer, which I use Shift to Layer.

Found this https://github.com/Dygmalab/Bazecor/issues/90 where someone figured out F20 is triggering XF86AudioMidMute in Linux. So, this may not need any custom QMK firmware at all, and could be as easy as assigning F20 to some key with VIA and see if that does what you need. F20 is available in the VIA Configure (keyboard icon) Tab under Special down on the lower left side.

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.

I’ve learned a lot from Seniply and Miryoku, both designed to take advantage of small keyboards. They both default to Colemak-DH, which is good.