dotfiles.git - Personal scripts and configuration files

	Commit message (Collapse)	Author	Age	Files	Lines
*	Correct prefix for b:undo_* variable	Tom Ryder	2017-11-08	1	-1/+1
\| \| \| \|	This was causing nasty errors whenever I started editing a Perl file.
*	Use "nunmap" not "unmap" for b:undo_* var	Tom Ryder	2017-11-08	1	-3/+3
\| \| \| \|	We only want to remove the normal mode mapping, since that's all we set.
*	Remove null command from b:undo_* variables	Tom Ryder	2017-11-08	1	-2/+2
\| \| \| \| \|	I didn't realise that a null command at the front of .e.g '\|cmd\|cmd2' printed the current line! Removed that.
*	Use consistent/thorough ftplugin/indent unloading	Tom Ryder	2017-11-08	1	-0/+6
\| \| \| \|	Unload all maps too, with silent! in case they don't exist.
*	Adjust plugin code layout a lot	Tom Ryder	2017-11-04	1	-6/+9
\| \| \| \| \| \| \| \| \| \| \| \| \|	Including renaming big_file.vim and accompanying functions yet again, to big_file_options.vim. Trying to keep complex autocmd and mapping definitions on long lines broken up semantically; definition and options on one line, patterns or mapping key on the next, and the command to run on the last. Also trying to make sure that <silent>, <buffer>, and <unique> are applied in the correct places, and that all mapping commands are using the :<C-U> idiom for the command prefix.
*	Break long lines in check/lint/tidy mappings	Tom Ryder	2017-11-04	1	-3/+8
\|
*	Make all lint/check/tidy maps local and silent	Tom Ryder	2017-11-04	1	-3/+3
\| \| \| \| \| \|	That is, apply <buffer> and <silent> to each of them, to make them only apply to the current buffer and to prevent them from echoing the command they're running.
*	Improve comments on check/lint/tidy maps	Tom Ryder	2017-11-03	1	-3/+3
\|
*	Use direct :write !cmd instead of shellescape()	Tom Ryder	2017-11-03	1	-11/+6
\| \| \| \| \| \| \| \| \|	This is a much better method of calling external programs on the buffer's contents, not just because it avoids the mess of :execute evaluation but also because it doesn't require that there actually be a filename for the current buffer. This drastically simplifies the HTML tidy(1) call in particular.
*	Use full ':execute' not just ':exe' in VimL	Tom Ryder	2017-11-03	1	-2/+2
\| \| \| \|	We should probably avoid this sort of abbreviation in scripts.
*	Check for availability of Vim shellescape()	Tom Ryder	2017-11-03	1	-6/+11
\| \| \| \| \|	It doesn't seem to be in very old Vims; worth testing for to avoid errors if I try to use the function.
*	Use <Leader>/<LocalLeader> correctly in Vim config	Tom Ryder	2017-11-03	1	-3/+3
\| \| \| \| \| \| \|	From ":help <LocalLeader>": > In a global plugin <Leader> should be used and in a filetype plugin > <LocalLeader>. "mapleader" and "maplocalleader" can be equal.
*	Move filetype-specific indent options into indent/	Tom Ryder	2017-10-30	1	-7/+0
\| \| \| \| \| \|	I'm still getting used to the structure of the configuration here, and had mistakenly put these indent-related settings into files in the ftplugin directory.
*	Add some more file-specific indent preferences	Tom Ryder	2017-10-30	1	-0/+7
\| \| \| \| \| \| \| \| \| \|	For some languages in which I write often: C, HTML, Perl, PHP, and shell scripts. All of these values presently match the defaults specified in config/indent.vim, but for languages I commonly use it's probably appropriate to have files to set the indent settings explicitly anyway, especially if we switched from a filetype with different values.
*	Move vim/after/ftplugin files into vim/ftplugin	Tom Ryder	2017-10-30	1	-0/+6
	None of the settings in here need to be run after the core configuration files are loaded, so I'll put them in a slightly more accessible or logical place. This adds a new target `install-vim-ftplugin`, and makes that a prerequisite of the `install-vim` target.