| 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.)
|
|
788d15e removed wasysym.
|
|
|
|
|
|
|
|
As of Org mode commit 329683861cc85aa,
org-clone-subtree-with-time-shift accepts a value of 0, which allows a
repeating subtree to be replaced with a non-repeating subtree and a
shifted, repeating subtree.
Rewrite org-clone-and-shift-by-repeater to use the new
org-clone-subtree-with-time-shift. As an added bonus, this means that
org-clone-and-shift-by-repeater now supports scheduled items and time
stamps, not just deadlines
|
|
|
|
|
|
Call org-agenda-do-context-action after jumping, just like
org-agenda-next-line.
|
|
|
|
|
|
|
|
|
|
|
|
The advantage of this over use km/export-wrapped-text with md buffer
is that it respects code blocks.
|
|
|
|
|
|
|
|
|
|
Search for whole heading line instead of using
org-find-exact-headline-in-buffer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I've set org-adapt-indentation to nil (b8ffd041f).
|
|
|
|
|
|
|
|
|
|
I've kept this as non-nil because I prefer planning info and drawers
to be indented at the level of headings. However, I don't indent
paragraphs of text (mostly for diffing purposes).
With recent Org changes [1-3], mixing these styles doesn't work well
because structure-modifying commands now adjust the paragraph
indentation even if the text is at column 0.
[1] cba2f0a2a3024ae5bf71e1a12ba99778a92902a2
[2] 83d8a2b16d1efc32f868897559452c0922906c67
[3] http://thread.gmane.org/gmane.emacs.orgmode/93597
|
|
I no longer need this advice because org-agenda-window-setup now [1]
takes the value 'only-window', which has the same effect.
[1] 7834a1ce66d3e60b9ecf5ad04a12d76d23cfbc5c
|
|
|
|
|
|
|
|
|
|
- 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/
|
|
|
|
|
|
|
|
|