This is my old vim config, I still use it where neovim is not available, but I will not be updating this any more. It may depend on some things from my dotfiles, at this tagged version https://github.com/davidosomething/dotfiles/releases/tag/last-old-vim
See the nvim config for more up-to-date stuff.
Don't use what you don't understand.
- Custom statusline with minimal junk, showing short directory
- FZF for Most Recently Used files and fuzzy file finder
- CoC for language server and misc utilities
- Neomake for non-language server makers/linters
- Language emphasis: JavaScript, VimL, PHP, HTML, SCSS (but not exclusive)
- Lazy loaded plugins and keybindings -- a brand new Vim instance opens in <200ms (without plugins Vim takes around 100ms)
- Lots more but you shouldn't use any of it unless you know what you're doing.
vim-plug plugins will be installed into $XDG_DATA_HOME/vim/vendor! Make
sure you have XDG environment variables set up.
Best used with rest of dotfiles. coc/extensions/dot.npmrc will enforce using
the main npmjs package registry. Commands in .vimrc will auto-install
plugins if curl is available.
Keep (g)vimrc (no dot in filename) in ~/.vim/ -- Vim knows to look in there.
Finally
:UpdateRemotePluginsif installing/upgrading python-based plugins:checkhealthto see if the python3 setup and plugins are working.
- Using
rtxto install and use a node. - When installing/updating plugins, vim-plug will automatically install the associated dependencies.
Comment out runtime! archlinux.vim from /etc/vimrc if you're on Arch Linux
(despite its pleas not to.)
Plugins settings are in plugin/ and after/* as appropriate. There
is generally a wrapper around them that checks for
dkoplug#IsLoaded('plugin-name').
<C-f>-- Expand snippet. I use<C-u>/<C-d>to jump pages instead.gsno longer sleeps. It's an operator prefix for vim-operator-surround.
| Key | Desc |
|---|---|
<A-b> |
:FZFBuffers |
<A-c> |
:FZFCommands |
<A-f> |
:FZFFiles - files from Vim's cwd |
<A-g> |
:FZFGrepper - custom, rg/ag with preview or git-grep |
<A-m> |
:FZFMRU - custom MRU |
<A-p> |
:FZFProject |
<A-p> |
:FZFProject - custom, :FZFFiles but from project root |
<A-r> |
:FZFRelevant |
<A-r> |
:FZFRelevant - custom, dirty/new files vs git master |
<A-t> |
:FZFTests - custom find test files near current path |
<A-v> |
:FZFVim - ~/.vim |
\ |
UI - :OverCommandLine |
See plugin/mappings.vim (and other plugin/* files) for other mappings.
Plan to remap these at some point
n <C-b>-- backward one screen (page)n <C-f>-- forward one screen (page)n zh/l-- useless wrap mode scroll
Adhere to vint and vim-vimlint linting rules.
Always try to keep as much in the main runtime as possible, using after/
sparingly (typically for setlocal ftplugin settings).
- Include
&cpoptionsguard if there are mappings - Use
<special>if the mapping key is special (irrespective of&cpoptions) - Use
<A-instead of<M-for alt/meta mappings g:DKO_FunctionName- DKO_PascalCases:FunctionName- PascalCaseautoload#FunctionName- PascalCaseg:dko_variable_name- dko_snake_case for my global variablesl:local_variable- snake_case function-local variabless:variable_name- snake_case for script-local variablesg:dko#variable_name- prefixed autoload-provided global variabledkoautocommandgroup- lowercasealphanumer1cnospaces- Include
dkoplug#Exists()ordkoplug#IsLoaded()checks if relying on plugins <Plug>(DKOMyPlugMapping)- Parentheses around<Plug>mapping names- The
augroupformine/plugins should beplugin-pluginname - The
augroupfor plugin settings should bedkopluginname - Bar continuation should have a space:
\ | {{next command }}