dotfiles VS miryoku

If you wanted to check anything else out, here's my i3 config, that appfetch.sh script, and my rofi themes

And here's a table with all those hotkeys laid out so I could keep track of them more easily: https://github.com/NicksIdeaEngine/dotfiles/blob/master/refs/linux/dotfiles/i3hotkeys.mkdn

Edit your ~/.Xmodmap file to something like this: https://github.com/NicksIdeaEngine/dotfiles/blob/master/.Xmodmap

My user_modules.ini file is right here but it's just more examples of the module above.

Here is that script.

lol I have an over-engineered multi-file neovim config that probably gets close to 500+ lines if I combine everything back into one file and remove all the extra space used to make it more readable. I've been apprehensive about switching to Lua but I know it needs to happen soon.

Here's my gtk-3.0/settings.ini file: https://github.com/NicksIdeaEngine/dotfiles/blob/master/.config/gtk-3.0/settings.ini

Layer 0 and 1 are for PC/Linux. On Linux, I use this .Xmodmap file ( https://github.com/NicksIdeaEngine/dotfiles/blob/master/.Xmodmap )to set up how that OS interprets CapsLock to give me an extra modifier key. Aside from that, there isn't anything I felt needed specification between PC/Linux.

Here is mine which replaces the Caps Lock key with Hyper along with some other stuff. https://github.com/NicksIdeaEngine/dotfiles/blob/master/.Xmodmap

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.