vim bundle notes
This is a collection -- a substantially revised collection -- of vim plugins and configuration that I use. It has been substatnially reduced from where it once was, simply as I'd concluded that I need to refactor, reassess, and ensure I use current and correct plugins, effectively.
(The older, sloppier vimrc is still availble under refs/attic/old-master. Note this refspec is not pulled by default.)
bundle/ for an always up-to-date, complete list :)
Local and private configuration information
We source the
~/.vimrc.local file at the end of this one such that
per-machine or private information may be stored (e.g. authentication
credentials and the like). This file is not and should never be stored in
Location and Installation
This repository is set up such that it can be installed as your
Running the contained
Makefile will set up the appropriate symlinks,
~/.vimrc and ensuring that an
~/.vimrc.local exists and
has restrictive permissions (rw-------, aka 0600).
Alternative locations (that is, not storing this repo in ~/.vim) is not
currently supported by the
Makefile, though could certainly be handled
trivially by hand.
Whenever pratical, external code and plugins are embedded and managed via git
submodules, and stashed under
bundle/. There are some submodules that
do not fit the standard layout; those are generally stored under
and synlinked into
bundle/ as appropriate.
submodules vs subtree
Note: I'm experimenting with squashed git subtrees at the moment, so a number of our included bundles will appear as squished merges of independent commit histories. This has pros and cons, not the least of which is not needing to worry about submodule init/update/etc, but I'm still "on the fence", as it were.
Some bundles are included as subtrees rather than submodules. Both have their (dis)advantages, but subtrees tend to be easier to include/remove.
Interfaces with web applications
We use the fantastic vitra plugin to interface
with Trac instances. Note that this requires the Trac XML-RPC interface to
be installed and active as well as the appropriate configuration information
LICENSE, COPYRIGHT and AUTHORSHIP
All code not written by Chris Weyl, including but not limited to included plugins, linked submodules, etc, and the like are copyright their respecitve creators and licensed under their terms. For information, please see any files in question for embedded information.
The remainder is copyright 2013 Chris Weyl email@example.com