dotvim - My vim configuration

Age	Commit message (Collapse)	Author
2018-03-07	git-blamer: Set `nowrap` on buffer	Teddy Wing
	In order to get the cursor lines to correctly match up horizontally in all cases, set 'nowrap' on the buffer. To set 'wrap' back, follow fugitive.vim's example: https://github.com/tpope/vim-fugitive/blob/f3ccb0c12ee4985b8808f83059830a24cc92821c/plugin/fugitive.vim#L2038-L2040
2018-03-07	git-blamer: Add `q` mapping to quit window	Teddy Wing
	Makes it just a bit easier to close the GitBlamer window. Since we shouldn't need macros in this panel it should be fine.
2018-03-07	git-blamer: Use `syncbind` to aid horizontal line alignment	Teddy Wing
	Adding `syncbind` appears to fix the bug where in certain cases the GitBlamer cursor line and the buffer cursor line weren't horizontally aligned.
2018-03-07	git-blamer: Use `cursor()` instead of `setpos()`	Teddy Wing
	Use the `cursor()` function to set the position of the cursor. This call is simpler than `setpos()`, and more descriptive than `execute l:top_line` (that was inspired by fugitive.vim, https://github.com/tpope/vim-fugitive/blob/f3ccb0c12ee4985b8808f83059830a24cc92821c/plugin/fugitive.vim#L2048-L2064)
2018-03-07	git-blamer: Align cursor lines of buffer and GitBlamer window	Teddy Wing
	Take the mechanism that Fugitive.vim uses: https://github.com/tpope/vim-fugitive/blob/f3ccb0c12ee4985b8808f83059830a24cc92821c/plugin/fugitive.vim#L2048-L2064 This positions the cursor lines on the same horizontal line so that blame information can be read on the same line as the code it corresponds to. Not sure, but it doesn't seem to work exactly right on one of my machines, but did appear to work correctly on another. Could just be the fault of 'wrap' though.
2018-03-07	git-blamer: Remove terminating whitespace	Teddy Wing
	I don't really like these any more.
2018-03-07	git-blamer: Fix bug causing `cursorbind` to be set on other windows	Teddy Wing
	In some instances with more than one window open, closing the GitBlamer window would cause other windows in the tab to have `cursorbind` (and presumably `scrollbind`) set. Fix the bug by setting `scrollbind` and `cursorbind` on the buffer (these are window-local variables, we'll have to find out if it's weird to set them on a buffer), and store the "restore" command in a buffer-local variable (local to the GitBlamer window).
2016-10-26	git-blamer: Open blame windows `leftabove`	Teddy Wing
	Based on my current Vim settings, splits open to the right (I have `splitright` turned on). This causes the blame window to open to the right of the file in question, which is weird, since normally that metadata appears to the left of the file. Open the Blamer split on the left by default to make the formatting more consistent with the normal `git blame` output.
2015-09-08	git-blamer: Use `git blame -w`	Teddy Wing
	Add the `-w` flag to our `git blame` call in order to ignore whitespace changes so we can see who originally introduced a line's change even if there were subsequent whitespace changes made to the line.
2015-07-23	vimrc: Move comment to git-blamer plugin	Teddy Wing
	Made more sense to move it there since all the functionality is now being performed in the plugin instead of in my vimrc.
2015-07-23	Add git-blamer plugin	Teddy Wing
	Create a plugin that runs a `git blame` and opens the result in a new vertical split. This one builds on a43d3caaea3682f58aee6dc295e48cca415067c5 but improves it by adding some extra niceties including moving to the line the cursor was on in the original file, setting appropriate flags so that the split doesn't appear in the buffer list and becomes non-modifiable, and setting cursor and scroll binding so that the buffers scroll together. An `autocmd` resets the original buffer to `noscrollbind` and `nocursorbind`.