| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
I had this set to global so I could jump to windows displayed in frames
of other monitors, but I didn't use this often and it had the
disadvantage of needing to type a letter for the current two-window
frame if there were any frames on other monitors.
|
|
|
|
- Use directory in compilation buffer name.
- Make recompile and display-buffer commands support for multiple
buffers, including compilation-last-buffer.
|
|
|
|
|
|
- Require that point is on either actual doi or "doi:".
- Use the regexp to deal with trailing punctuation.
|
|
I prefer this binding to '^', but I didn't realize that similar
behavior is available using dired-jump for a Dired buffer.
|
|
|
|
|
|
|
|
|
|
|
|
This is more consistent with its one-key binding in other modes (e.g.,
magit-log-mode and gnus-summary-mode).
|
|
|
|
Keep all continued statements and expression at the original level.
|
|
|
|
It's not bound to a key with any other binding.
|
|
|
|
A revision doesn't make sense because the '--all' flag is being
passed.
|
|
|
|
|
|
|
|
- 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/
|
|
|
|
|
|
|
|
|
|
|
|
Magit commit a44ed1b9c3b0ffa09b988cb8305da0105e4702ea
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As of commit 7e945107ced488344fd78cd1388cf000b29733e8 in Org mode,
restoring windows should work better with sticky agenda buffers.
|