| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This reverts commit e53becab23aeae58b4d156f9d45428342c15a4b1.
|
|
|
|
This reverts commit ad8a9a3d94c3553d59e3d4ad2b99580d8d395c21 and
e158f7f14b061eb731ea44ddac1f09f1008380de.
|
|
|
|
|
|
With 5f4f111cd, I replaced by old buffer cleanup functions with
whitespace-mode. This resulted in similar behavior, but empty lines at
the end of the buffer were no longer deleted. The 'empty' option for
whitespace-style will do this, but it also deletes empty lines at the
beginning of the buffer, which I don't want.
Add delete-trailing-whitespace to km/cleanup-buffer so that trailing
whitespace is removed.
|
|
These modifications are based off of Drew Adam's comment function [1].
The main change in behavior from my old function is that whole lines of
the region are commented even when the beginning or end of the region is
not at the beginning or end of the line.
[1] http://permalink.gmane.org/gmane.emacs.devel/181816
|
|
Whenever I use goto-line, it's because I already have the line number,
so I don't need the feedback. If I just wanted to jump to a visible
line, I'd use ace-jump-mode.
|
|
|
|
|
|
I use this for er/expand-region.
|
|
- 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
|
|
- Activate global whitespace-mode. When not allowing the buffer to be
cleaned up, use more annoying whitespace indicators.
- Use whitespace-cleanup as cleanup function. Except for trailing
whitespace, this should cover what km/cleanup-buffer was doing and
more.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Accidentally made two copies of code in
ad80f4b4896b13d23b488146af4e4df6354191a7.
|
|
|
|
|
|
|
|
|
|
|
|
This is enabled by default in Emacs 24.4.
|
|
|
|
|
|
Needed to install 'subr+ to avoid void variable
`filter-buffer-subtring-function'.
|
|
|
|
|
|
|
|
|
|
If this is set to global, frames in other desktops (even invisible ones)
are used to generate the jump choices.
|
|
Removing ido-vertical because if it is active, some links in the lower
portion of the window are cutoff.
|
|
There was only one binding left in insert map, so it didn't make much
sense to keep around.
|
|
|
|
Removed line and list completion functions, which are almost never what
I intend to complete. This should also take care of the clash with
paredit mode (since these multi-word expansions shouldn't occur
anymore), so I'm deleting `he-paredit-fix'.
|
|
|
|
|
|
|
|
|
|
|
|
|