Nearly every Neo/Vim configuration you find online is composed of a single,
giant vimrc
file. But this one is different: it's [modular], relying on
Vim's behavior of loading all plugin/**/*.vim
files on startup to cleanly
partition your settings, mappings, bundles, and other configuration out into
separate little files that all focus on a single topic and do one thing well.
-
Modularity of bundles, filetypes, colorschemes, and Vim settings.
-
Lazy loading of filetype-specific bundles to start Vim up quickly.
-
Parallel installation and updating of bundles from Git repositories.
-
Easy upgrades with intelligent and automated Git conflict resolution.
-
Shell scripts for bundle management: insert, delete, rename, and more.
-
The [master] branch is a "bare bones" template for anyone to start with. [master]: https://github.com/sunaku/.vim/tree/master#readme
-
The [basics] branch is a rudimentary configuration of the Standard Vim. [basics]: https://github.com/sunaku/.vim/tree/basics#readme
-
The [qwerty] branch is the usual configuration meant for QWERTY typists. [qwerty]: https://github.com/sunaku/.vim/tree/qwerty#readme
-
The [dvorak] branch is an unusual configuration meant for Dvorak typists. [dvorak]: https://github.com/sunaku/.vim/tree/dvorak#readme
bin/*
scripts automate common tasks. See below for their usage manuals.
-
**/*.get
files specify URLs of Git repositories to clone for your bundles. -
**/*.set
files specify branch names or commit SHAs to check out from Git. -
**/*.run
files specify shell commands to run after updating your bundles. -
bundle/*/*/
directories are eagerly loaded Vim scripts; see Unbundle. -
ftbundle/*/*/
directories are lazily loaded, filetype-specific bundles.
-
plugin/**/*.vim
configure Vim before it finishes starting up. -
bundle/*/*.vim
configure your bundles before they are loaded. -
ftbundle/*/*.vim
configure your ftbundles before they are loaded. -
ftplugin/{*,/*}.vim
configure your filetypes when they are loaded. -
recolor/*.vim
configure your colorschemes after they are applied. -
after/plugin/**/*.vim
configure Vim after it finishes starting up.
-
Git 1.5+
-
[POSIX] environment (Linux, BSD, MacOSX, etc.) [POSIX]: http://pubs.opengroup.org/onlinepubs/9699919799/
Special note to Microsoft Windows users: simply
- replace
~/.vim
with%USERPROFILE%\vimfiles
- replace
~/.vimrc
with%USERPROFILE%\_vimrc
in all commands listed throughout this document.
- replace
-
xargs with support for the
-r
command-line option:Do not run the command if there are no arguments. Normally the command is executed at least once even if there are no arguments.
Backup your configuration:
mv ~/.vim ~/.vim.bak
mv ~/.config/nvim ~/.config/nvim.bak # for NeoVim
Install this configuration:
git clone https://github.com/sunaku/.vim.git ~/.vim
ln -s ~/.vim ~/.config/nvim # for NeoVim
cd ~/.vim
bin/setup
Select a Git branch to use:
bin/setup # bare bones
bin/setup basics # bare bones + basic config
bin/setup qwerty # bare bones + basic config + the usual
bin/setup dvorak # bare bones + basic config + the usual + my flair
See usage information:
bin/usage
See usage information for provided SCRIPT:
bin/usage SCRIPT
Add bundle from URL under CATEGORY:
bin/insert URL bundle/CATEGORY
Add bundle from URL under CATEGORY with BUNDLE_NAME:
bin/insert URL bundle/CATEGORY/BUNDLE_NAME
Add ftbundle from URL for FILETYPE:
bin/insert URL ftbundle/FILETYPE
Add ftbundle from URL for FILETYPE with BUNDLE_NAME:
bin/insert URL ftbundle/FILETYPE/BUNDLE_NAME
Add bundle from Github USER/REPO under CATEGORY:
bin/insert USER/REPO bundle/CATEGORY
Add bundle from Github USER/REPO under CATEGORY with BUNDLE_NAME:
bin/insert USER/REPO bundle/CATEGORY/BUNDLE_NAME
Add ftbundle from Github USER/REPO for FILETYPE:
bin/insert USER/REPO ftbundle/FILETYPE
Add ftbundle from Github USER/REPO for FILETYPE with BUNDLE_NAME:
bin/insert USER/REPO ftbundle/FILETYPE/BUNDLE_NAME
Rename bundles with names matching BUNDLE_NAME (regexp):
bin/rename BUNDLE_NAME
Rename all bundles from the comfort of Vim:
bin/rename-editor BUNDLE_NAME
Rename a *.get
file from its current name to a new one:
bin/rename-fromto CURRENT_GET_FILE NEW_GET_FILE
Delete bundles with names matching BUNDLE_NAME (regexp):
bin/delete BUNDLE_NAME
Lists untracked *.get
files and bundles lacking *.get
files:
bin/orphans
Deletes untracked *.get
files and bundles lacking *.get
files:
bin/clean # asks you for confirmation
bin/clean -f # no confirmation; force it
Update installed bundles and ftbundles:
bin/update
Update this Vim configuration framework:
bin/rebase # asks to confirm bin/clean
bin/rebase -f # no confirmation; force it
Do all that periodically via crontab(1):
@daily cd ~/.vim && bin/rebase -f && bin/update
Lock a BUNDLE to a certain Git COMMIT to prevent it from being updated:
cd BUNDLE
git checkout COMMIT
Unlock a locked BUNDLE so that it can be updated again:
cd BUNDLE
git checkout master
The usage manual for each script is reproduced here, for your convenience.
Deletes untracked *.get
files and bundles lacking *.get
files,
as well as any files or directories seen as waste by git-clean(1).
Usage: bin/clean # asks you for confirmation
Usage: bin/clean -f # no confirmation; force it
Deletes existing bundles whose names match the given regular expression.
Usage: bin/delete [OPTIONS_FOR_GREP...] BUNDLE_NAME_REGEXP
Inserts a new bundle, optionally named BUNDLE_NAME, into the given CATEGORY. You can specify USER/REPO in place of URL to insert from GitHub repositories.
Usage: bin/insert [URL|USER/REPO] [ft]bundle/CATEGORY[/BUNDLE_NAME]
Usage: bin/insert URL bundle/CATEGORY
Usage: bin/insert URL bundle/CATEGORY/BUNDLE_NAME
Usage: bin/insert URL ftbundle/FILETYPE
Usage: bin/insert URL ftbundle/FILETYPE/BUNDLE_NAME
Usage: bin/insert USER/REPO bundle/CATEGORY
Usage: bin/insert USER/REPO bundle/CATEGORY/BUNDLE_NAME
Usage: bin/insert USER/REPO ftbundle/FILETYPE
Usage: bin/insert USER/REPO ftbundle/FILETYPE/BUNDLE_NAME
Lists untracked *.get
files and bundles lacking *.get
files.
Usage: bin/orphans
Replays local commits atop the newest changes from upstream.
Usage: bin/rebase # asks to confirm bin/clean
Usage: bin/rebase -f # no confirmation; force it
Usage: git-rebase-autocon [TARGET] [ARGUMENTS_FOR_GIT_REBASE...]
Rebases the given TARGET while automatically resolving conflicts by substituting empty-tree commits labeled "fixup!" that log all conflicting hunks in their commit messages in git-diff(1) format.
If TARGET is not specified, the upstream tracking branch is used. Optional ARGUMENTS_FOR_GIT_REBASE... are passed to git-rebase(1).
Documented at https://sunaku.github.io/git-rebase-autocon.html
Rebases the main branches, going from conventional to divergent.
Renames existing bundles whose names match the given regular expression.
Usage: bin/rename [OPTIONS_FOR_GREP...] BUNDLE_NAME_REGEXP
At the prompt, edit the bundle location and press ENTER to rename it so. If you no longer wish to rename the bundle, just press ENTER to skip it. If you made a mistake and want to abort the rename, press Control and C.
Lets you rename all *.get files in one fell swoop, from the comfort of Vim.
Usage: bin/rename-editor [OPTIONS_FOR_VIM...]
Simply rename the lines you're interested in and then save and quit, but be careful not to change the order or amount of lines presented in the editor!
To cancel without performing any renames, type "ggdG:wqa" followed by ENTER.
Attempts to rename bundles back to their URL basenames.
Usage: bin/rename-editor-urlname [OPTIONS_FOR_VIM...]
Renames the given *.get file and all associated files to the new name.
Usage: bin/rename-fromto CURRENT_GET_FILE NEW_GET_FILE
Activates the given BRANCH and installs any bundles it defines.
Usage: bin/setup [BRANCH]
Usage: bin/setup # bare bones
Usage: bin/setup basics # bare bones + basic config
Usage: bin/setup qwerty # bare bones + basic config + the usual
Usage: bin/setup dvorak # bare bones + basic config + the usual + my flair
Usage: bin/update [BUNDLE_NAME|DIRECTORY|GET_FILE]...
Usage: env UPDATE_BUNDLES_SEQUENTIALLY=1 bin/update
Clones or updates the Git repositories specified in ./**/*.get
files:
optionally matching the given BUNDLE_NAME, DIRECTORY, or GET_FILE path,
starting from the most recently modified file down to the earliest one,
checking out the branch or commit named in related ./**/*.set
files.
After that, it runs corresponding ./**/*.run
scripts for those repos.
This is done in parallel, at up to half of the maximum process limit,
unless the UPDATE_BUNDLES_SEQUENTIALLY
environment variable is set.
Displays help and usage information for this and fellow scripts.
Usage: bin/usage [SCRIPT]
Formats usage information from all scripts for injection into README.
- [Plugin Layout in the Dark Ages][modular] by Steve Losh. [modular]: http://learnvimscriptthehardway.stevelosh.com/chapters/42.html