summaryrefslogtreecommitdiff
path: root/snippets/sh-mode
diff options
context:
space:
mode:
authorKyle Meyer <kyle@kyleam.com>2015-02-01 18:54:41 -0500
committerKyle Meyer <kyle@kyleam.com>2015-02-02 22:42:24 -0500
commit3993e88764bfe3415b0a7bff83a5ba630cf9cfe1 (patch)
treef5987e7820352f4b4f29c142a99537fa6d009626 /snippets/sh-mode
parent9eb55edf10df005beaef0393f3a03bddf4c116b8 (diff)
downloademacs.d-3993e88764bfe3415b0a7bff83a5ba630cf9cfe1.tar.gz
Rework key chords
- Use letter pairs that are rare in both directions. For really common commands, try to keep my fingers on home row. - Remove some key chords for less frequent commands. For Projectile, just bind switching projects and the commander because most other things are available with one more key from the commander. My strategy for key chord bindings was to lead with ',' or ';' and then follow with any letter. The idea was that, with the languages and coding conventions I was using at the time, when I inserted a comma or semicolon, they were usually followed by a non-letter (typically a space or a new line). But, this is actually not a good way to go about this because Key chord mode accepts the two-letter combination in either order. In practice, I didn't end up unintentionally calling a command too often, but it did happen enough to be slightly annoying. John Cook recently posted a table [1] of bigram frequencies, which is a good starting point for updating my key chords. [1]: http://www.johndcook.com/blog/2015/02/01/rare-bigrams/
Diffstat (limited to 'snippets/sh-mode')
0 files changed, 0 insertions, 0 deletions