-
Notifications
You must be signed in to change notification settings - Fork 18
About my own 'king' configuration
This is my own configuration, which fixes pretty much every keyboard problem I ever had.
It has evolved over 20 years, and is probably overwhelming for most people.
Check the default capsicain.ini (or capsicain.kingcon.ini, which is a duplicate)
to see how I write configs.
My kingcon ini uses most of what capsicain can do. If you want to define cursor controls, or diacritics, check how I do it first.
(takes too long now to explain all the features... it's mostly described in my 'Solutions' below)
If you want to play with it, you should know:
- CapsLock down + IJKL gives you cursor keys.
YU O. NM H;are the 'other' cursor control keys. - ALT + (the alpha keys) gives you all special characters
- \ is Enter, / is Shift. Create "/" characters with ALT + F and J
- ALT and WIN are used for special things. Tap-then-press the Alt key for real ALT; same with WIN.
Other than that, your keyboard should work as usual. All 'extra' features are combos you don't know (like Tab+1 = F1).
If you want to create your own advanced setup, you might be interested in my experience...
- can't touch type code on international layout
- can't type international characters on US layout
- cursor and all edit keys require slow hand moves
- Control kinda sucks. But you can't just get used to a HHKB, because that will mess you up on laptops
- many laptops and small keyboards don't follow the IBM layout standard
- switching keyboards (ANSI/ISO, Apple/IBM, non-standard boards) is difficult
- lots of finger stretching (especially with the pinkies)
- RSI (Repeated Stress Syndrome, numb fingers)
- (AHK fails with low-level apps, but that's generally solved with capsicain)
Last but not least: computer keyboards were designed, when 99.9% of the population still used typewriters, so they wanted to keep things the same. And typewriter standards have been defined 100 years ago when typewriters were really bad.
Many things have been taken over from typewriters, that make no sense beyond "people don't want to relearn".
I think you can easily come up with a setup that improves on the status quo.
US-English is the original layout. All other keyboard layouts are 'translations in software'.
Your capsicain.ini must match the Windows layout. You could write an .ini that works with a Windows German layout, but then you would have to send the keycombo "AltGr+8" to create [, when every keyboard has a dedicated [ key (which Windows translates to Ü for German layouts) .
Lots of potential confusion; and if you run Photoshop, brush size changes with the [ key, and not an imaginary "Ü" key.
You lose some international characters when you go US, but you can revive them all with a capsicain config.
Yes, QWERTY was created so that typewriter hammers don't jam so often.
Yes, DVORAK and COLMAK are better.
But a) I have so much time invested in QWERTY skills,
and b) you just can't get away from Qwerty, it's everywhere.
If I was learning to touch type today, I'd look into the alternatives.
Not for any speed improvements, but for the joy of typing in a relaxed rhythm with small finger movements.
//TODO