summaryrefslogtreecommitdiff
path: root/lisp
AgeCommit message (Collapse)Author
2015-02-15Fix docstrings for diff commandsKyle Meyer
2015-02-15Add org-{next,previous}-item bindingsKyle Meyer
2015-02-15Give winner-undo a key chordKyle Meyer
2015-02-15Enable Winner modeKyle Meyer
2015-02-15Don't use global-unset-keyKyle Meyer
2015-02-13Rewrite gnus-catchup-and-goto-next-groupKyle Meyer
2015-02-13Enable set-mark-command-repeat-popKyle Meyer
2015-02-13Remove unnecessary lambdas from hooksKyle Meyer
2015-02-13Don't adapt Org indentationKyle Meyer
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
2015-02-11Use 'only-window' for org-agenda-window-setupKyle Meyer
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
2015-02-11gnus: Add ido variants for group and topic jumpingKyle Meyer
2015-02-11Bind ace-jump-mode to 'j' in Org agendaKyle Meyer
2015-02-11gnus: Rewrite bury functionsKyle Meyer
2015-02-09Change aw-scope to frameKyle Meyer
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.
2015-02-09Add command compile-in-home-dirKyle Meyer
2015-02-09Rewrite compilation commandsKyle Meyer
- Use directory in compilation buffer name. - Make recompile and display-buffer commands support for multiple buffers, including compilation-last-buffer.
2015-02-07Add command copy-doi-as-killKyle Meyer
2015-02-07Add 'C-c C-f' binding for org-agenda-follow-modeKyle Meyer
2015-02-04Rewrite doi-at-pointKyle Meyer
- Require that point is on either actual doi or "doi:". - Use the regexp to deal with trailing punctuation.
2015-02-04Remove additional binding for dired-up-directoryKyle Meyer
I prefer this binding to '^', but I didn't realize that similar behavior is available using dired-jump for a Dired buffer.
2015-02-04Fix misplaced commentKyle Meyer
2015-02-04Add dired-view-file-other-window commandKyle Meyer
2015-02-03Merge babel and contacts settings to main Org fileKyle Meyer
2015-02-03Add save-some-buffers variantKyle Meyer
2015-02-03Correct typo in commentKyle Meyer
2015-02-02Bind ace-jump-mode to 'j' in View modeKyle Meyer
This is more consistent with its one-key binding in other modes (e.g., magit-log-mode and gnus-summary-mode).
2015-02-02Rewrite grep-hide-headerKyle Meyer
2015-02-02Change default ESS styleKyle Meyer
Keep all continued statements and expression at the original level.
2015-02-02Use auto-complete as yas fallback in Python modeKyle Meyer
2015-02-02Turn off yas fallback behaviorKyle Meyer
It's not bound to a key with any other binding.
2015-02-02Rebind find-functionKyle Meyer
2015-02-02Don't read revision for magit-log-all-branchesKyle Meyer
A revision doesn't make sense because the '--all' flag is being passed.
2015-02-02Add binding for org-clone-and-shift-by-repeaterKyle Meyer
2015-02-02Add command zsh-toggle-ansi-term-homeKyle Meyer
2015-02-02Rework some Projectile bindingsKyle Meyer
2015-02-02Rework key chordsKyle Meyer
- 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/
2015-02-02Install whole-line-or-regionKyle Meyer
2015-02-02Reposition mode callsKyle Meyer
2015-02-02Merge Org capture and agenda sectionsKyle Meyer
2015-02-02Move Org agenda key binding to right locationKyle Meyer
2015-02-01Add kill buffer variantKyle Meyer
2015-01-31Update for renamed Magit commandKyle Meyer
Magit commit a44ed1b9c3b0ffa09b988cb8305da0105e4702ea
2015-01-29Split init-buffile.elKyle Meyer
2015-01-29Use hook for fullscreen MagitKyle Meyer
2015-01-28Send up to line, not point, to Python shellKyle Meyer
2015-01-28Explicitly require cl-libKyle Meyer
2015-01-27Rewrite diff advice as separate functionKyle Meyer
2015-01-27Load latex-mode, not tex-mode, for *.tex filesKyle Meyer
2015-01-27Remove duplicate binding in gnus-summary-mode-mapKyle Meyer
2015-01-27Don't advise clone-indirect-buffer-other-windowKyle Meyer
Generated by cgit. Colors based on the Modus themes.