vim, git, aws and other three-letter words

Software Development Notes

Keyboard Layouts: Links, Articles

Various examples of keyboard layouts.

Qwerty, Dvorak, Colemak   folded

Alternative layouts try to make typing more pleasant by placing more often accessed keys in the home row: clipboard-20261108T200206.png

  • The Dvorak Keyboard
  • Colemak
  • HandsDown - alanreiser.com/handsdown/
  • More layouts
  • Qwerty, Dvorak, or Colemak? : ergodox
    • Using vim feels natural with both Colemak and Dvorak after some training. However, if you use any vim bindings for your browser, like vimium or surfing key, jk will be a nightmare for you.
    • it's not just the bottom row (zxcvb) that is unchanged, Colemak manages to leave a number of other keys in the same place as qwerty (q, w, a, h, m) whilst retaining one of the most efficient keyboard layouts you can switch to.
    • I typed with Dvorak for 10 years and then eventually switched to Colemak which I have been using for the last 5 years and I'm a software engineer as well. I think either layout is better than Qwerty in my opinion. Dvorak will have you switching hands more often and Colemak has more "finger rolls" across the keyboard which I personally like more, but that is a preference thing.
    • Well as a software developer (Javascript among others) I asked myself the same question, I ended up with this :
    • I have tried both Dvorak and Colemak when I got my Ergodox EZ. Unlike popular belief, neither have problems with using vim or the function keys. These just come naturally once you get used to. Also, both feels comfy when it gets to typing. Those minor wins does not matter at all.
      • However, I do find Dvorak has an edge on two aspect. First is the jk position. Since the Ergodox is so good and using so much space on your table, chances are you might want to use vim bindings for your browser too. The jk position is a total nightmare when I used Colemak. It simply makes my index finger on my right hand painful. For using vim it does not matter as j k are not used often but if you use vim binding for browsers, it will be a pain.
      • The other is that the idea of alternating hands are more universal among languages while Colemak is only optimised for English. When I type other languages like Japanese in Romaji, or Chinese in pinyin, or other languages, Dvorak still feels great as you still alternate hands a lot. Whereas Colemak is giving no edge on that.
      • I'm personally a huge fan of Colemak DH on all my keebs at this point because of how comfy it is when learned. Dvorak focuses on hand alternation (left, right, left) while Colemak focuses on inward rolls (pinky, ring, middle index). So specific layout is up to you. But you may be less frustrated with Colemak for that and because of the decreased key change.
      • Here's my Ergodox Dvorak layout, if you want to see some ideas: https://configure.zsa.io/ergodox-ez/layouts/aWM5b/latest/0
      • I started using Colemak-DH (with switched m/k) when I built my split ortho keyboard and I'm entirely pleased with it. I feel like I'm almost always on the home row and the common rolling actions are both super fast and very satisfying. The m/k switch is a specific adaptation with respect to matrix style keyboards and it shows. Having used qwerty extensively and Workman a little and regular Colemak a little I can say that this particular variant is entirely superior. Vim keybindings are fine for me, with the caveat that I use arrow keys for navigation and those arrow keys are mapped to where wasd are on a qwerty keyboard, on a layer I access with my left thumb. I have escape under a thumb and : where left shift usually is and consequently I can escape to normal mode and type ':wq' at the speed of light.
    • Been using Dvorak for 15+ years, but 2 months ago decided to give BEAKL15 a try. It is extremely comfortable especially for English typing, and the symbol layer is fantastic for Software Developers (I program in Java).
      • Still not sure about the number row though. I have been using an Ergodox for 3 years and prefer F-keys on the base layer (where numbers would traditionally be) and numbers as a numpad layout on a different layer. This has served me very well.
      • Anyway, here is my layout for more inspiration. https://configure.zsa.io/ergodox-ez/layouts/BNpaO/latest/1
        • Several layouts on layers: qwerty, dvorak, beakl15
        • Symbols layer - check how parenthesis are placed
        • Strange: instead of Shift, there is a shifted layer + momentary toggle (press and hold) to switch to it - so it looks like it works the same way as shift
          • Is this because of a custom layout?
    • ErgoDox: Day 48 - Asylum - mentions some practical dvorak problems

QMK Features: Layers, Home Row Mods, Combos, etc   folded

QMK Basics – Thomas Baart and info

Layer toggle types   folded

  • Momentary (MO):
    • This is like a Shift key. Hold down a momentary toggle, and you're taken to another layer. Let go, and you drop back to layer 0.
    • As soon as you let go of the key, the layer is deactivated and you pop back out to the previous layer.
    • When you apply this to a key, that same key must be set as KC_TRNS on the destination layer. Otherwise, you won't make it back to the original layer when you release the key (and you'll get a keycode sent).
    • You can only switch to layers above your current layer. If you're on layer 0 and you use MO(1), that will switch to layer 1 just fine. But if you include MO(3) on layer 5, that won't do anything for you – because layer 3 is lower than layer 5 on the stack.
  • Toggle (TG):
    • This is similar to a Caps Lock. Tap once, and you're moved to that layer. You'll stay on that layer until you tap the layer toggle key again. Depending on the type, you'll momentarily/permanently have access to the key bindings of that specific layer.
  • One-shot (OSL):
    • Tap this key, and you're moved to the layer. Tap a single key on the layer, and you will then be sent back to layer 0. Like Shift, but without having to hold down two keys at once.
    • This type of layer switch allows you to either tap it and get the next layer for one key press or hold it and continue to get that next layer until you release it. It's wonderful for the types of keys we'll be looking at on Layer 1.
  • OSM(mod) - this is a "one shot" modifier. - sticky shift
    • So let's say you have your left Shift key defined as OSM(MOD_LSFT). Tap it, let go, and Shift is "on" – but only for the next character you'll type. So to write "The", you don't need to hold down Shift – you tap it, tap t, and move on with life. And if you hold down the left Shift key, it just works as a left Shift key, as you would expect (so you could type THE). There's also a magical, secret way to "lock" a modifier by tapping it multiple times. If you want to learn more about that, open an issue. :)
  • Tap-Toggle (TT):
    • A combination of Momentary and Toggle. Hold this key, and the layer is active only as long as you hold it. Tap it briefly, and you're moved to the destination layer until you tap it again.
  • Direct switch (TO):
    • All other layer switches go up (allow you to switch from layer 0 to layer 1, for example). TO is the only one which also allows you to switch down (from layer 3 to layer 2, for example).
  • Meh / Hyper keys
    • System-level shortcuts to switch to apps
  • order matters: OSL + OSM ignores OSL; OSM + OSL works as expected Issue #6943

A guide to home row mods (notes)   folded

  • Notes
    • Why not GACS (shift is used more often than Ctrl)
      • The points are not very convincing in my case
      • On a 40% layout another important key(s) is the layer switch (Sym like I have or lower/raise like in Planck)
      • Auto-shift makes shift not needed
      • I almost never use Alt (might be due to other flows I use)
  • Summary
    • Mods that are placed on the home row
    • It is more convenient and ergonomic
    • How to use home row mods?
      • Home row mods order
        • SCGA (Shift-Ctrl-Gui-Alt) - order like on the regular keyboard
        • GASC (Gui-Alt-Shift-Ctrl) - often used keys are on stronger fingers
          • Why not GACS (shift is used more often than Ctrl)?
            • 1. The index finger is the finger that is responsible for the biggest amount of alpha keys so if you use the index finger to hold Shift, you'll have to swap hands if you want to type any of the six keys
              • I did not understand this point, what is "swap hands" in this context?
              • Is this about the possibility to hold the shift with right hand and type the upper-case letter with the same hand? So "swap hands" is holding shift on the left and typing on the right and vice versa
              • In that case, I always only consider the "swap hands" variant
              • 2. With GASC it is easier to do both Alt-Shift and Ctrl-Shift (adjacent keys in both cases)
              • 3. (weak point) We can have "main" thumb shift, so GASC shift in the home row is just to use in combinations with Alt and Ctrl
              • 4. The position of GUI next to Alt allows for easy GUI+Alt+Arrows, a keyboard shortcut used in some DEs for switching between virtual desktops/workspaces.
              • 5. Do not load the index finger too much
            • Additional note: This works out great on ortholinear and vertically staggered keyboards but if you use a row-staggered keyboard, you may find that you're suddenly unable to copy and paste one-handedly.
              • Not sure why
              • GACS - order following the keys frequency (Miryoku uses it)
              • CAGS - good for Mac OS where GUI is used in place of Ctrl
      • Using home row mods with QMK
        • Use MT (mod tap) keys: MT(mod_code, key_code)
        • On code level, there are shortcut macros: MT(MOD_LGUI, KC_A) = LGUI_T(KC_A)
    • Tap Hold configuration settings

Retro tapping   folded

  • MT(Mod, X) will send X if the key is held longer than tapping term. Retro Tap thus gives another way to trigger the tapping function of mod-taps. With this option, you can get away with a very short tapping term.
  • Tapping term is short, so it is easier to do Hold
  • What if we set tapping term to zero? (so any keypress is "Hold")
    • When used in combination with other keys, mod will always be Hold
  • What if we set tapping term to infinity? (so any keypress is "Tap")
    • We can get "nested hold, rolling tap" behavior with
    • MT = Nested=Hold, Rolling=Tap -> PERMISSIVE_HOLD + IGNORE_MOD_TAP_INTERRUPT
    • LT = Nested=Hold, Rolling=Tap -> PERMISSIVE_HOLD
    • This is also a behavior that looks natural to me, so it might be possible to go without tapping term
      • When should keys be processed in this case? Should we wait until all are released?
      • What if we are on a layer or holding Shift?

Tap-Hold Configuration   folded

  • TAPPING_TERM 200 Tapping Term - determines what is a tap and what is a hold
    • TAPPING_TERM_PER_KEY + get_tapping_term() function to define term per key
  • #define PERMISSIVE_HOLD Permissive Hold - do not take tapping term into account for mod taps (hold mod, press and release another key will always work, even if done faster than tapping term)
    • Makes tap and hold keys (like Mod Tap) work better for fast typists, or for high TAPPING_TERM settings
    • Note: always enabled for TAPPING_TERM >= 500
    • For Instance:
      • SFT_T(KC_A) Down
      • KC_X Down
      • KC_X Up
      • SFT_T(KC_A) Up
      • Normally, if you do all this within the TAPPING_TERM, by default 200ms, this will be registered as ax by the firmware and host system.
      • With permissive hold enabled, this modifies how this is handled by considering the Mod Tap keys as a Mod if another key is tapped, and would be registered as X (SHIFT+x).
    • Permissive Hold, and two keymaps by agbell · Pull Request #1359 · qmk/qmk_firmware
    • Note: it looks like permissive hold only works for MT (mod tap), but not for LT
      • Maybe not, this is mentioned in PR comments, but it may have changed since then
      • PERMISSIVE_HOLD_PER_KEY + get_permissive_hold() to define permissive hold per key
  • #define IGNORE_MOD_TAP_INTERRUPT Ignore Mod Tap Interrupt - allow to release modifier before the other key (rolling through mod and key), need to hold both down during the tapping term (or is this the opposite, where enabling ignore mod tap interrupt makes rolling input produce regular keys and enables mod ONLY AFTER waiting for the tapping term)
    • Setting Ignore Mod Tap Interrupt requires holding both keys for the TAPPING_TERM to trigger the hold function (the mod)

    • For Instance:

      • SFT_T(KC_A) Down
      • KC_X Down
      • SFT_T(KC_A) Up
      • KC_X Up

      Normally, this would send X (SHIFT+x). With Ignore Mod Tap Interrupt enabled, holding both keys are required for the TAPPING_TERM to register the hold action.

      • Bad example, as "normally" here does not say if that is done before or after the tapping term
      • A quick tap will output ax in this case, while a hold on both will still output X (SHIFT+x).
    • Note: This only concerns modifiers and not layer switching keys.
      • Not sure why, logically layers should work exactly the same as regular modifiers
      • IGNORE_MOD_TAP_INTERRUPT_PER_KEY + get_ignore_mod_tap_interrupt to set per key

  • Ignore Mod Tap Interrupt + Permissive Hold Modifier added when rolling (modifier released first) instead of waiting for other key release (like in permissive hold) or when both keys are held for tapping term

    • If you have Permissive Hold enabled, as well, this will modify how both work.
    • The regular key has the modifier added if the first key is released first or if both keys are held longer than the TAPPING_TERM.

    Not sure, but probably this means that:

    • SFT_T(KC_A) Down - KC_X Down - SFT_T(KC_A) Up - KC_X Up
    • will always produce Shift-x?
    • Isn't it more logical to always have SFT Down - X down - X Up - Shift Up to trigger Shift-x?
    • Again, the description is confusing: "The regular key has the modifier added if the first key is released first" - what is the 'first' key here, is this always a mod key?

  • #define TAPPING_FORCE_HOLD Tapping Force Hold - disable key repeat on tap followed by tap+hold (act as hold instead of key repeat)

    • Usually, this is a way to activate the repeat function on mod taps

    But it does not work well, for example, when I have backspace on a layer that is activated with space

    • When I type "xyz" and want to delete it, I do
    • x - y - z - left space - hold left space - right space (as backspace)
    • so here I have the "left space - hold left space" which would trigger space repeat normally, while I do not want this
    • TAPPING_FORCE_HOLD_PER_KEY + get_tapping_force_hold for per key setting
  • Retro Tapping - releasing the Mod key without pressing another will send the original keycode even if it is outside the tapping term (regular behavior: #define RETRO_TAPPING: no output)
    • For instance, holding for tapping term and releasing LT(2, KC_SPACE) will output space (by default - nothing)
    • RETRO_TAPPING_PER_KEY + get_retro_tapping for per key setting
  • okke's Cheatsheet on MT and LT
  • [Feature Request] Permissive Hold and Ignore Mod Tap Interrupt for LT · Issue #8971 · qmk/qmk_firmware
  • Questions
    • permissive hold is always enabled when tapping term > 500 - how is the tapping term used then? tapping term determines what is a tap and what is a hold, but now hold ignores the tapping term
    • is retro tapping useful for anything else? the obvious case is a habit to often keep keys pressed for too long like when thinking about something
    • am I understanding ignore mod tap interrupt right?
      • permissive hold: nested key press ("mod down - key down - key up - mod up") = always mod+key (hold action)
      • ignore mod tap interrupt: rolling key press ("mod down - key down - mod up - key up") holding keys longer than tapping term = mod+key
      • ignore mod tap interrupt + permissive hold: rolling key press ("mod down - key down - mod up - key up") = always mod+key
        • maybe: both nested and rolling key press are counted as mod (so this is just a "stronger" option than permissive hold)
      • there is also a discussion here [Feature Request] Permissive Hold and Ignore Mod Tap Interrupt for LT · Issue #8971 · qmk/qmk_firmware
      • In general: it looks like these two settings are overcomplicated, and could be a multi-choice option instead of the combination of settings
        • Default: wait for tapping term (shorter - regular key, longer - mod)
        • Other key is pressed / released while mod is held (regardless of time) - apply mod
        • Other key is pressed while mod is held (can be released after, regardless of time) - apply mod
        • if QMK has unit tests, it would be great to emulate and check how it works via test (set some settings, run key sequences, check the result) - to be sure how it works
        • but sigprof just tested manually, using 499 tapping term
        • AND they are adding alternative options for LT mods (current options are for MT, but affect LT too)

The Leader key: A new kind of modifier

Combos

Retro Shift

Allows using AutoShift with dual-mod keys (hold longer and let go - shifted symbol, use with another key - mod)

Swappiness

  • Swap Hands - QMK
    • Set SWAP_HANDS_ENABLE in the Makefile and define a hand_swap_config entry in your keymap.
    • Now whenever the ACTION_SWAP_HANDS command key is pressed the keyboard is mirrored.
    • For instance, to type "Hello, World" on QWERTY you would type ^Ge^s^s^w^c W^wr^sd
  • One-handed solutions? : ErgoMechKeyboards
  • Do you also mirror the order of the keys? So, for QWERTY:
    • POIUY YUIOP
    • ;LKJH HJKL;
    • .,MN NM,.
    • (mirrored) (unmirrored)
    • Yes, I mirrored. Basically making sure you hit same key with same finger on opposite hand. On right hand P is under pinky, on left mirrored layout P is under pinky as well. If you know how to touch type, you'll easily remember which finger you use for which key, without having to look at the keyboard, even when using opposite hand.

[home key mods + fast typing] 111WPM   folded

home key mods + fast typing: 111WPM on a Dactyl Manuform with homerow mods and Colemak-DHM : ErgoMechKeyboards

  • I've enabled pretty much every tap hold configuration setting and tweaked the tapping term on a per key basis based on frequency of the modifier and the tendency of some of my fingers to rest longer on the key. This is, for example, why I added 200ms to the tapping term of the HOME_I key as my ring finger tended to rest oddly long on the key when typing n-grams such as "ion".
  • Recently, in an effort to lower the tapping term for my shift modtaps even more, I've been toying with canceling the effect of shift on the adjacent keys. So if I hit "N" with right shift on, I probably intended to write "en" instead. So in those cases, instead of sending "N", the firmware sends "en". As a consequence, capital "N" can only be typed with the opposite shift.

Related:

Layouts - Articles, Tips   folded

Steno   folded

Ergonomics   folded

  • PSA: Thumbs can get overuse injuries
  • Thoughts on Mechanical Keyboards and the ZSA Moonlander - Mastering Emacs
  • Is curling your thumb under your other fingers comfortable? (e.g. Corne, Iris, Lily58, etc.)
  • Having wrist pain, should I change keyboard? : MechanicalKeyboards
    • Let's take a look at human hands:
      • Hands are symmetrical.
      • Fingers have varying length: middle fingers are the longest and little fingers are the shortest by a significant margin.
      • Thumbs are opposable, i.e., move along an arc entirely different from the other fingers.
      • Standard keyboards go against all three points: keys are in straight rows (2-3) that are asymmetrically offset (1). 0 points
      • Ortholinear keyboards are symmetrical (1), but have keys in straight rows (2), including the spacebar row (3). 1 point
      • Only very few ortholinear designs, e.g., Zen, have some thumb keys at least at an angle. 2 points
      • Finally, there are actually ergonomic keyboards that are symmetrical (1), have key columns offset or at different height (2) and have dedicated thumb keys in an arc or on another plane (3). 3 points
      • examples: Maltron, Kinesis Advantage, Dactyl, Manuform, Keyboardio Model 01, to a lesser degree ErgoDox-based designs like ReDox, ErgoDash or Iris
    • tl;dr (layouts)
      • Dvorak and Maltron are backed up by research.
      • "Enthusiast layouts" (Colemak, Workman, Norman,…) are arbitrary.
      • The layout is only one piece of a larger puzzle, along with ergonomic keyboards; there's posture, cognition, software environment,…

Software   folded

Tags: kbd

Tags