| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
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/
|
|
|
|
|
|
|
|
|
|
As of commit 7e945107ced488344fd78cd1388cf000b29733e8 in Org mode,
restoring windows should work better with sticky agenda buffers.
|
|
- 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This variable is usually non-nil because I run Emacs as a daemon, but
since I use these bindings frequently, I want to make sure
org-use-speed-commands is always non-nil.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
magit-visit was removed a while ago [1], so this isn't doing anything.
Currently, there are multiple functions to advise [2]. Instead of doing
that, I'll just call org-reveal (C-c C-r).
[1] 81c6b881d9e4e93442677d6e2183c7f2cc47887a
[2] 2dc3965e74eabe53763f208809a9dae3105c1149
|
|
|
|
Switched to Org in 71642c8257e367d82631cbb740b1325fe44df50f.
|
|
Almost every time I used `km/open-main-orgfile', I would jump to the
"Inbox" heading right after, so just have the command do that for me.
|
|
The main motivation for this is to set org-refile-targets to the value
specified in ~/notes/.dir-locals.el.
|
|
org-agenda-files can be a directory, which allows the files that make up
the agenda to be changed without having to change emacs configuration
files. So, instead of using org-agenda-file-to-front, which modifies
org-agenda-files in custom.el, the new agenda file can just be linked to
the agenda directory.
|
|
Aside from 'agenda', all other types still match their default values.
|
|
|