| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit 808e4c576e1b751570ea8436bc89b697ea2fa35a.
I was mistaken about being mistaken. Calling avy-goto-subword-1 in Org
with folded headings assigns candidates to hidden text.
|
|
I added this because avy-goto-subword-1 was offering invisible text in
Org mode buffers as candidates. However, this no longer seems to be the
case (and perhaps I was mistaken to begin with or there was something
else going on, because I don't see an obvious commit in the avy repo
that changes this behavior.)
|
|
Only changed main binding in f88d106fc3.
|
|
|
|
This is more consistent with its one-key binding in other modes (e.g.,
magit-log-mode and gnus-summary-mode).
|
|
- 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/
|
|
- Add pages and more headings for large files.
- Try to use consistent order for file (or page) structure.
* Loading
* Settings
* Hooks
* Any mode activation or function calls
* My functions
* Key bindings
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|